<?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>Sun, 04 Oct 2026 10:23:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37989 — net: phy: leds: fix memory leak</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37989</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: phy: leds: fix memory leak&lt;/p&gt;
&lt;p&gt;A network restart test on a router led to an out-of-memory condition,
which was traced to a memory leak in the PHY LED trigger code.&lt;/p&gt;
&lt;p&gt;The root cause is misuse of the devm API. The registration function
(phy_led_triggers_register) is called from phy_attach_direct, not
phy_probe, and the unregister function (phy_led_triggers_unregister)
is called from phy_detach, not phy_remove. This means the register and
unregister functions can be called multiple times for the same PHY
device, but devm-allocated memory is not freed until the driver is
unbound.&lt;/p&gt;
&lt;p&gt;This also prevents kmemleak from detecting the leak, as the devm API
internally stores the allocated pointer.&lt;/p&gt;
&lt;p&gt;Fix this by replacing devm_kzalloc/devm_kcalloc with standard
kzalloc/kcalloc, and add the corresponding kfree calls in the unregister
path.&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: phy: leds: fix memory leak&lt;/p&gt;
&lt;p&gt;A network restart test on a router led to an out-of-memory condition,
which was traced to a memory leak in the PHY LED trigger code.&lt;/p&gt;
&lt;p&gt;The root cause is misuse of the devm API. The registration function
(phy_led_triggers_register) is called from phy_attach_direct, not
phy_probe, and the unregister function (phy_led_triggers_unregister)
is called from phy_detach, not phy_remove. This means the register and
unregister functions can be called multiple times for the same PHY
device, but devm-allocated memory is not freed until the driver is
unbound.&lt;/p&gt;
&lt;p&gt;This also prevents kmemleak from detecting the leak, as the devm API
internally stores the allocated pointer.&lt;/p&gt;
&lt;p&gt;Fix this by replacing devm_kzalloc/devm_kcalloc with standard
kzalloc/kcalloc, and add the corresponding kfree calls in the unregister
path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37989</guid>
    </item>
  </channel>
</rss>
