<?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://cve.radiocsirt.org</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>Fri, 02 Oct 2026 15:28:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-10431</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-10431</link>
      <description>bdu:2026-10431</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-10431</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53834</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53834</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53834</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>EUVD-2026-312281</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312281</link>
      <description>EUVD-2026-312281</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312281</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53834</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53834</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2023-53834</guid>
    </item>
    <item>
      <title>GHSA-vwr3-mpmm-8xqx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vwr3-mpmm-8xqx</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-vwr3-mpmm-8xqx</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:0263-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53834</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53834</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: adc: ina2xx: avoid NULL pointer dereference on OF device match The affected lines were resulting in a NULL pointer dereference on our platform because the device tree contained the following list of compatible strings:     power-sensor@40 {         compatible = &amp;#34;ti,ina232&amp;#34;, &amp;#34;ti,ina231&amp;#34;;         ...     }; 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. 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; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 156 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: adc: ina2xx: avoid NULL pointer dereference on OF device match The affected lines were resulting in a NULL pointer dereference on our platform because the device tree contained the following list of compatible strings:     power-sensor@40 {         compatible = &amp;#34;ti,ina232&amp;#34;, &amp;#34;ti,ina231&amp;#34;;         ...     }; 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. 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://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53834</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2765 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765</guid>
    </item>
  </channel>
</rss>
