<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:17:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99446 — phy: core: Fix race-condition between _of_phy_get() and try_module_get()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99446</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;phy: core: Fix race-condition between _of_phy_get() and try_module_get()&lt;/p&gt;
&lt;p&gt;Sashiko asked during a patch review if the existing usage pattern had a
race condition; specifically in of_phy_get() if it was possible between
returning from _of_phy_get() and running try_module_get() that a module
might be unbound leading to use-after-free.&lt;/p&gt;
&lt;p&gt;Looking at the code this appears to be so, there is no linkage between the
phy and module under a synchronisation primitive.&lt;/p&gt;
&lt;p&gt;Using the phy_provider_mutex in phy_get() will ensure there is a link between
the returned phy pointer and the module_get() bumping the module reference
count.&lt;/p&gt;
&lt;p&gt;Amend phy_get(), of_phy_get() and devm_of_phy_get_by_index() to fix the
same usage pattern.&lt;/p&gt;
&lt;p&gt;phy_provider_unregister() must take the phy_provider_mutex so amending
phy_get()/of_phy_get() to take that same mutex guarantees there is no
use-after-free.&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;phy: core: Fix race-condition between _of_phy_get() and try_module_get()&lt;/p&gt;
&lt;p&gt;Sashiko asked during a patch review if the existing usage pattern had a
race condition; specifically in of_phy_get() if it was possible between
returning from _of_phy_get() and running try_module_get() that a module
might be unbound leading to use-after-free.&lt;/p&gt;
&lt;p&gt;Looking at the code this appears to be so, there is no linkage between the
phy and module under a synchronisation primitive.&lt;/p&gt;
&lt;p&gt;Using the phy_provider_mutex in phy_get() will ensure there is a link between
the returned phy pointer and the module_get() bumping the module reference
count.&lt;/p&gt;
&lt;p&gt;Amend phy_get(), of_phy_get() and devm_of_phy_get_by_index() to fix the
same usage pattern.&lt;/p&gt;
&lt;p&gt;phy_provider_unregister() must take the phy_provider_mutex so amending
phy_get()/of_phy_get() to take that same mutex guarantees there is no
use-after-free.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99446</guid>
    </item>
  </channel>
</rss>
