<?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 13:58:34 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03492</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03492</link>
      <description>bdu:2026-03492</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03492</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — 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-2025-avi-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-310460</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310460</link>
      <description>EUVD-2026-310460</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310460</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49285</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49285</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: accel: mma8452: use the correct logic to get mma8452_data&lt;/p&gt;
&lt;p&gt;The original logic to get mma8452_data is wrong, the *dev point to
the device belong to iio_dev. we can&amp;#39;t use this dev to find the
correct i2c_client. The original logic happen to work because it
finally use dev-&amp;gt;driver_data to get iio_dev. Here use the API
to_i2c_client() is wrong and make reader confuse. To correct the
logic, it should be like this&lt;/p&gt;
&lt;p&gt;struct mma8452_data *data = iio_priv(dev_get_drvdata(dev));&lt;/p&gt;
&lt;p&gt;But after commit 8b7651f25962 (&amp;#34;iio: iio_device_alloc(): Remove
unnecessary self drvdata&amp;#34;), the upper logic also can&amp;#39;t work.
When try to show the avialable scale in userspace, will meet kernel
dump, kernel handle NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;So use dev_to_iio_dev() to correct the logic.&lt;/p&gt;
&lt;p&gt;Dual fixes tags as the second reflects when the bug was exposed, whilst
the first reflects when the original bug was introduced.&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: accel: mma8452: use the correct logic to get mma8452_data&lt;/p&gt;
&lt;p&gt;The original logic to get mma8452_data is wrong, the *dev point to
the device belong to iio_dev. we can&amp;#39;t use this dev to find the
correct i2c_client. The original logic happen to work because it
finally use dev-&amp;gt;driver_data to get iio_dev. Here use the API
to_i2c_client() is wrong and make reader confuse. To correct the
logic, it should be like this&lt;/p&gt;
&lt;p&gt;struct mma8452_data *data = iio_priv(dev_get_drvdata(dev));&lt;/p&gt;
&lt;p&gt;But after commit 8b7651f25962 (&amp;#34;iio: iio_device_alloc(): Remove
unnecessary self drvdata&amp;#34;), the upper logic also can&amp;#39;t work.
When try to show the avialable scale in userspace, will meet kernel
dump, kernel handle NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;So use dev_to_iio_dev() to correct the logic.&lt;/p&gt;
&lt;p&gt;Dual fixes tags as the second reflects when the bug was exposed, whilst
the first reflects when the original bug was introduced.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49285</guid>
    </item>
    <item>
      <title>GHSA-m279-rgmp-gm5j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m279-rgmp-gm5j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: accel: mma8452: use the correct logic to get mma8452_data&lt;/p&gt;
&lt;p&gt;The original logic to get mma8452_data is wrong, the *dev point to
the device belong to iio_dev. we can&amp;#39;t use this dev to find the
correct i2c_client. The original logic happen to work because it
finally use dev-&amp;gt;driver_data to get iio_dev. Here use the API
to_i2c_client() is wrong and make reader confuse. To correct the
logic, it should be like this&lt;/p&gt;
&lt;p&gt;struct mma8452_data *data = iio_priv(dev_get_drvdata(dev));&lt;/p&gt;
&lt;p&gt;But after commit 8b7651f25962 (&amp;#34;iio: iio_device_alloc(): Remove
unnecessary self drvdata&amp;#34;), the upper logic also can&amp;#39;t work.
When try to show the avialable scale in userspace, will meet kernel
dump, kernel handle NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;So use dev_to_iio_dev() to correct the logic.&lt;/p&gt;
&lt;p&gt;Dual fixes tags as the second reflects when the bug was exposed, whilst
the first reflects when the original bug was introduced.&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: accel: mma8452: use the correct logic to get mma8452_data&lt;/p&gt;
&lt;p&gt;The original logic to get mma8452_data is wrong, the *dev point to
the device belong to iio_dev. we can&amp;#39;t use this dev to find the
correct i2c_client. The original logic happen to work because it
finally use dev-&amp;gt;driver_data to get iio_dev. Here use the API
to_i2c_client() is wrong and make reader confuse. To correct the
logic, it should be like this&lt;/p&gt;
&lt;p&gt;struct mma8452_data *data = iio_priv(dev_get_drvdata(dev));&lt;/p&gt;
&lt;p&gt;But after commit 8b7651f25962 (&amp;#34;iio: iio_device_alloc(): Remove
unnecessary self drvdata&amp;#34;), the upper logic also can&amp;#39;t work.
When try to show the avialable scale in userspace, will meet kernel
dump, kernel handle NULL pointer dereference.&lt;/p&gt;
&lt;p&gt;So use dev_to_iio_dev() to correct the logic.&lt;/p&gt;
&lt;p&gt;Dual fixes tags as the second reflects when the bug was exposed, whilst
the first reflects when the original bug was introduced.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m279-rgmp-gm5j</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:1176-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:1176-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-2025:1176-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49285</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49285</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 144 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: accel: mma8452: use the correct logic to get mma8452_data The original logic to get mma8452_data is wrong, the *dev point to the device belong to iio_dev. we can&amp;#39;t use this dev to find the correct i2c_client. The original logic happen to work because it finally use dev-&amp;gt;driver_data to get iio_dev. Here use the API to_i2c_client() is wrong and make reader confuse. To correct the logic, it should be like this   struct mma8452_data *data = iio_priv(dev_get_drvdata(dev)); But after commit 8b7651f25962 (&amp;#34;iio: iio_device_alloc(): Remove unnecessary self drvdata&amp;#34;), the upper logic also can&amp;#39;t work. When try to show the avialable scale in userspace, will meet kernel dump, kernel handle NULL pointer dereference. So use dev_to_iio_dev() to correct the logic. Dual fixes tags as the second reflects when the bug was exposed, whilst the first reflects when the original bug was introduced.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 144 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: accel: mma8452: use the correct logic to get mma8452_data The original logic to get mma8452_data is wrong, the *dev point to the device belong to iio_dev. we can&amp;#39;t use this dev to find the correct i2c_client. The original logic happen to work because it finally use dev-&amp;gt;driver_data to get iio_dev. Here use the API to_i2c_client() is wrong and make reader confuse. To correct the logic, it should be like this   struct mma8452_data *data = iio_priv(dev_get_drvdata(dev)); But after commit 8b7651f25962 (&amp;#34;iio: iio_device_alloc(): Remove unnecessary self drvdata&amp;#34;), the upper logic also can&amp;#39;t work. When try to show the avialable scale in userspace, will meet kernel dump, kernel handle NULL pointer dereference. So use dev_to_iio_dev() to correct the logic. Dual fixes tags as the second reflects when the bug was exposed, whilst the first reflects when the original bug was introduced.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49285</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2107 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2107</guid>
    </item>
  </channel>
</rss>
