<?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>Wed, 30 Sep 2026 01:28:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72396 — hwmon: adm1275: Prevent reading uninitialized stack</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72396</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;hwmon: adm1275: Prevent reading uninitialized stack&lt;/p&gt;
&lt;p&gt;While adding support for the ROHM BD127X0 hot-swap controllers, sashiko
reported an error in device-name comparison, which can lead to reading
uninitialized stack memory.&lt;/p&gt;
&lt;p&gt;Quoting Sashiko:&lt;/p&gt;
&lt;p&gt;This is a pre-existing issue, but I noticed that just before this block in
adm1275_probe(), there might be an out-of-bounds stack read:&lt;/p&gt;
&lt;p&gt;ret = i2c_smbus_read_block_data(client, PMBUS_MFR_MODEL, block_buffer);
    if (ret &amp;lt; 0) { ... }
    for (mid = adm1275_id; mid-&amp;gt;name[0]; mid++) {
            if (!strncasecmp(mid-&amp;gt;name, block_buffer, strlen(mid-&amp;gt;name)))
                    break;
    }&lt;/p&gt;
&lt;p&gt;Since i2c_smbus_read_block_data() reads up to 32 bytes into the
uninitialized stack array block_buffer without appending a null
terminator, strncasecmp() could read past the valid bytes returned in ret.&lt;/p&gt;
&lt;p&gt;For example, if the device returns a shorter string like &amp;#34;adm12&amp;#34;, checking
it against &amp;#34;adm1275&amp;#34; up to the length of &amp;#34;adm1275&amp;#34; will continue reading
into uninitialized stack bounds.&lt;/p&gt;
&lt;p&gt;Prevent reading uninitialized memory by zeroing the stack array.&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;hwmon: adm1275: Prevent reading uninitialized stack&lt;/p&gt;
&lt;p&gt;While adding support for the ROHM BD127X0 hot-swap controllers, sashiko
reported an error in device-name comparison, which can lead to reading
uninitialized stack memory.&lt;/p&gt;
&lt;p&gt;Quoting Sashiko:&lt;/p&gt;
&lt;p&gt;This is a pre-existing issue, but I noticed that just before this block in
adm1275_probe(), there might be an out-of-bounds stack read:&lt;/p&gt;
&lt;p&gt;ret = i2c_smbus_read_block_data(client, PMBUS_MFR_MODEL, block_buffer);
    if (ret &amp;lt; 0) { ... }
    for (mid = adm1275_id; mid-&amp;gt;name[0]; mid++) {
            if (!strncasecmp(mid-&amp;gt;name, block_buffer, strlen(mid-&amp;gt;name)))
                    break;
    }&lt;/p&gt;
&lt;p&gt;Since i2c_smbus_read_block_data() reads up to 32 bytes into the
uninitialized stack array block_buffer without appending a null
terminator, strncasecmp() could read past the valid bytes returned in ret.&lt;/p&gt;
&lt;p&gt;For example, if the device returns a shorter string like &amp;#34;adm12&amp;#34;, checking
it against &amp;#34;adm1275&amp;#34; up to the length of &amp;#34;adm1275&amp;#34; will continue reading
into uninitialized stack bounds.&lt;/p&gt;
&lt;p&gt;Prevent reading uninitialized memory by zeroing the stack array.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72396</guid>
    </item>
  </channel>
</rss>
