<?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 19:12:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64228 — net: ethtool: phy: avoid NULL deref when PHY driver is unbound</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64228</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: ethtool: phy: avoid NULL deref when PHY driver is unbound&lt;/p&gt;
&lt;p&gt;phydev-&amp;gt;drv can become NULL while the phy_device is still attached to
its net_device, namely after the PHY driver is unbound via sysfs:&lt;/p&gt;
&lt;p&gt;echo &amp;lt;mdio_id&amp;gt; &amp;gt; /sys/bus/mdio_bus/drivers/&amp;lt;phy_drv&amp;gt;/unbind&lt;/p&gt;
&lt;p&gt;phy_remove() clears phydev-&amp;gt;drv but doesn&amp;#39;t call phy_detach(), so the
phy_device stays in the link topology xarray and ethnl_req_get_phydev()
still hands it back. ETHTOOL_MSG_PHY_GET then oopses on:&lt;/p&gt;
&lt;p&gt;rep_data-&amp;gt;drvname = kstrdup(phydev-&amp;gt;drv-&amp;gt;name, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;drvname is already treated as optional by phy_reply_size(),
phy_fill_reply() and phy_cleanup_data(), so just skip the allocation
when there is no driver bound.&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: ethtool: phy: avoid NULL deref when PHY driver is unbound&lt;/p&gt;
&lt;p&gt;phydev-&amp;gt;drv can become NULL while the phy_device is still attached to
its net_device, namely after the PHY driver is unbound via sysfs:&lt;/p&gt;
&lt;p&gt;echo &amp;lt;mdio_id&amp;gt; &amp;gt; /sys/bus/mdio_bus/drivers/&amp;lt;phy_drv&amp;gt;/unbind&lt;/p&gt;
&lt;p&gt;phy_remove() clears phydev-&amp;gt;drv but doesn&amp;#39;t call phy_detach(), so the
phy_device stays in the link topology xarray and ethnl_req_get_phydev()
still hands it back. ETHTOOL_MSG_PHY_GET then oopses on:&lt;/p&gt;
&lt;p&gt;rep_data-&amp;gt;drvname = kstrdup(phydev-&amp;gt;drv-&amp;gt;name, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;drvname is already treated as optional by phy_reply_size(),
phy_fill_reply() and phy_cleanup_data(), so just skip the allocation
when there is no driver bound.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64228</guid>
    </item>
  </channel>
</rss>
