<?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>Tue, 29 Sep 2026 16:55:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53834 — iio: adc: ina2xx: avoid NULL pointer dereference on OF device match</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53834</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;iio: adc: ina2xx: avoid NULL pointer dereference on OF device match&lt;/p&gt;
&lt;p&gt;The affected lines were resulting in a NULL pointer dereference on our
platform because the device tree contained the following list of
compatible strings:&lt;/p&gt;
&lt;p&gt;power-sensor@40 {
        compatible = &amp;#34;ti,ina232&amp;#34;, &amp;#34;ti,ina231&amp;#34;;
        ...
    };&lt;/p&gt;
&lt;p&gt;Since the driver doesn&amp;#39;t declare a compatible string &amp;#34;ti,ina232&amp;#34;, the OF
matching succeeds on &amp;#34;ti,ina231&amp;#34;. But the I2C device ID info is
populated via the first compatible string, cf. modalias population in
of_i2c_get_board_info(). Since there is no &amp;#34;ina232&amp;#34; entry in the legacy
I2C device ID table either, the struct i2c_device_id *id pointer in the
probe function is NULL.&lt;/p&gt;
&lt;p&gt;Fix this by using the already populated type variable instead, which
points to the proper driver data. Since the name is also wanted, add a
generic one to the ina2xx_config table.&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;iio: adc: ina2xx: avoid NULL pointer dereference on OF device match&lt;/p&gt;
&lt;p&gt;The affected lines were resulting in a NULL pointer dereference on our
platform because the device tree contained the following list of
compatible strings:&lt;/p&gt;
&lt;p&gt;power-sensor@40 {
        compatible = &amp;#34;ti,ina232&amp;#34;, &amp;#34;ti,ina231&amp;#34;;
        ...
    };&lt;/p&gt;
&lt;p&gt;Since the driver doesn&amp;#39;t declare a compatible string &amp;#34;ti,ina232&amp;#34;, the OF
matching succeeds on &amp;#34;ti,ina231&amp;#34;. But the I2C device ID info is
populated via the first compatible string, cf. modalias population in
of_i2c_get_board_info(). Since there is no &amp;#34;ina232&amp;#34; entry in the legacy
I2C device ID table either, the struct i2c_device_id *id pointer in the
probe function is NULL.&lt;/p&gt;
&lt;p&gt;Fix this by using the already populated type variable instead, which
points to the proper driver data. Since the name is also wanted, add a
generic one to the ina2xx_config table.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53834</guid>
    </item>
  </channel>
</rss>
