<?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 07:50:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38027 — regulator: max20086: fix invalid memory access</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38027</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;regulator: max20086: fix invalid memory access&lt;/p&gt;
&lt;p&gt;max20086_parse_regulators_dt() calls of_regulator_match() using an
array of struct of_regulator_match allocated on the stack for the
matches argument.&lt;/p&gt;
&lt;p&gt;of_regulator_match() calls devm_of_regulator_put_matches(), which calls
devres_alloc() to allocate a struct devm_of_regulator_matches which will
be de-allocated using devm_of_regulator_put_matches().&lt;/p&gt;
&lt;p&gt;struct devm_of_regulator_matches is populated with the stack allocated
matches array.&lt;/p&gt;
&lt;p&gt;If the device fails to probe, devm_of_regulator_put_matches() will be
called and will try to call of_node_put() on that stack pointer,
generating the following dmesg entries:&lt;/p&gt;
&lt;p&gt;max20086 6-0028: Failed to read DEVICE_ID reg: -121
kobject: &amp;#39;\xc0$\xa5\x03&amp;#39; (000000002cebcb7a): is not initialized, yet
kobject_put() is being called.&lt;/p&gt;
&lt;p&gt;Followed by a stack trace matching the call flow described above.&lt;/p&gt;
&lt;p&gt;Switch to allocating the matches array using devm_kcalloc() to
avoid accessing the stack pointer long after it&amp;#39;s out of scope.&lt;/p&gt;
&lt;p&gt;This also has the advantage of allowing multiple max20086 to probe
without overriding the data stored inside the global of_regulator_match.&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;regulator: max20086: fix invalid memory access&lt;/p&gt;
&lt;p&gt;max20086_parse_regulators_dt() calls of_regulator_match() using an
array of struct of_regulator_match allocated on the stack for the
matches argument.&lt;/p&gt;
&lt;p&gt;of_regulator_match() calls devm_of_regulator_put_matches(), which calls
devres_alloc() to allocate a struct devm_of_regulator_matches which will
be de-allocated using devm_of_regulator_put_matches().&lt;/p&gt;
&lt;p&gt;struct devm_of_regulator_matches is populated with the stack allocated
matches array.&lt;/p&gt;
&lt;p&gt;If the device fails to probe, devm_of_regulator_put_matches() will be
called and will try to call of_node_put() on that stack pointer,
generating the following dmesg entries:&lt;/p&gt;
&lt;p&gt;max20086 6-0028: Failed to read DEVICE_ID reg: -121
kobject: &amp;#39;\xc0$\xa5\x03&amp;#39; (000000002cebcb7a): is not initialized, yet
kobject_put() is being called.&lt;/p&gt;
&lt;p&gt;Followed by a stack trace matching the call flow described above.&lt;/p&gt;
&lt;p&gt;Switch to allocating the matches array using devm_kcalloc() to
avoid accessing the stack pointer long after it&amp;#39;s out of scope.&lt;/p&gt;
&lt;p&gt;This also has the advantage of allowing multiple max20086 to probe
without overriding the data stored inside the global of_regulator_match.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38027</guid>
    </item>
  </channel>
</rss>
