<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T02:16:24.523209+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38027</id>
    <title>CVE-2025-38027 — regulator: max20086: fix invalid memory access</title>
    <updated>2026-10-04T02:16:24.726909+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>regulator: max20086: fix invalid memory access</p>
<p>max20086_parse_regulators_dt() calls of_regulator_match() using an
array of struct of_regulator_match allocated on the stack for the
matches argument.</p>
<p>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().</p>
<p>struct devm_of_regulator_matches is populated with the stack allocated
matches array.</p>
<p>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:</p>
<p>max20086 6-0028: Failed to read DEVICE_ID reg: -121
kobject: '\xc0$\xa5\x03' (000000002cebcb7a): is not initialized, yet
kobject_put() is being called.</p>
<p>Followed by a stack trace matching the call flow described above.</p>
<p>Switch to allocating the matches array using devm_kcalloc() to
avoid accessing the stack pointer long after it's out of scope.</p>
<p>This also has the advantage of allowing multiple max20086 to probe
without overriding the data stored inside the global of_regulator_match.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38027"/>
  </entry>
</feed>
