<?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>Thu, 01 Oct 2026 04:33:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39719 — iio: imu: bno055: fix OOB access of hw_xlate array</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39719</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: imu: bno055: fix OOB access of hw_xlate array&lt;/p&gt;
&lt;p&gt;Fix a potential out-of-bounds array access of the hw_xlate array in
bno055.c.&lt;/p&gt;
&lt;p&gt;In bno055_get_regmask(), hw_xlate was iterated over the length of the
vals array instead of the length of the hw_xlate array. In the case of
bno055_gyr_scale, the vals array is larger than the hw_xlate array,
so this could result in an out-of-bounds access. In practice, this
shouldn&amp;#39;t happen though because a match should always be found which
breaks out of the for loop before it iterates beyond the end of the
hw_xlate array.&lt;/p&gt;
&lt;p&gt;By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be
sure we are iterating over the correct length.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: imu: bno055: fix OOB access of hw_xlate array&lt;/p&gt;
&lt;p&gt;Fix a potential out-of-bounds array access of the hw_xlate array in
bno055.c.&lt;/p&gt;
&lt;p&gt;In bno055_get_regmask(), hw_xlate was iterated over the length of the
vals array instead of the length of the hw_xlate array. In the case of
bno055_gyr_scale, the vals array is larger than the hw_xlate array,
so this could result in an out-of-bounds access. In practice, this
shouldn&amp;#39;t happen though because a match should always be found which
breaks out of the for loop before it iterates beyond the end of the
hw_xlate array.&lt;/p&gt;
&lt;p&gt;By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be
sure we are iterating over the correct length.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39719</guid>
    </item>
  </channel>
</rss>
