<?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>Sat, 03 Oct 2026 18:42:07 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11512</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11512</link>
      <description>bdu:2026-11512</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11512</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-71199</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71199</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-71199</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-315238</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315238</link>
      <description>EUVD-2026-315238</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315238</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71199</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71199</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;st-&amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_dev through iio_device_unregister but
quite a bit later. While the work mentioned above will be used. The
sequence of operations that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| at91_adc_workq_handler
at91_adc_remove                      |
iio_device_unregister(indio_dev)     |
//free indio_dev a bit later         |
                                     | iio_push_to_buffers(indio_dev)
                                     | //use indio_dev&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in at91_adc_remove.&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: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;st-&amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_dev through iio_device_unregister but
quite a bit later. While the work mentioned above will be used. The
sequence of operations that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| at91_adc_workq_handler
at91_adc_remove                      |
iio_device_unregister(indio_dev)     |
//free indio_dev a bit later         |
                                     | iio_push_to_buffers(indio_dev)
                                     | //use indio_dev&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in at91_adc_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71199</guid>
    </item>
    <item>
      <title>GHSA-gf86-6w2v-6jr9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gf86-6w2v-6jr9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;st-&amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_dev through iio_device_unregister but
quite a bit later. While the work mentioned above will be used. The
sequence of operations that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| at91_adc_workq_handler
at91_adc_remove                      |
iio_device_unregister(indio_dev)     |
//free indio_dev a bit later         |
                                     | iio_push_to_buffers(indio_dev)
                                     | //use indio_dev&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in at91_adc_remove.&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: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;st-&amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_dev through iio_device_unregister but
quite a bit later. While the work mentioned above will be used. The
sequence of operations that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| at91_adc_workq_handler
at91_adc_remove                      |
iio_device_unregister(indio_dev)     |
//free indio_dev a bit later         |
                                     | iio_push_to_buffers(indio_dev)
                                     | //use indio_dev&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in at91_adc_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gf86-6w2v-6jr9</guid>
    </item>
    <item>
      <title>OESA-2026-3155 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3155</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: accel: bmc150: Fix irq assumption regression&lt;/p&gt;
&lt;p&gt;The code in bmc150-accel-core.c unconditionally calls
bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,
such as on the runtime PM resume path giving a kernel
splat like this if the device has no interrupts:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
  address 00000001 when read&lt;/p&gt;
&lt;p&gt;PC is at bmc150_accel_set_interrupt+0x98/0x194
LR is at __pm_runtime_resume+0x5c/0x64
(...)
Call trace:
bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108
bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc
__iio_update_buffers from enable_store+0x84/0xc8
enable_store from kernfs_fop_write_iter+0x154/0x1b4&lt;/p&gt;
&lt;p&gt;This bug seems to have been in the driver since the beginning,
but it only manifests recently, I do not know why.&lt;/p&gt;
&lt;p&gt;Store the IRQ number in the state struct, as this is a common
pattern in other drivers, then use this to determine if we have
IRQ support or not.(CVE-2025-68330)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;amp;st-&amp;amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: accel: bmc150: Fix irq assumption regression&lt;/p&gt;
&lt;p&gt;The code in bmc150-accel-core.c unconditionally calls
bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,
such as on the runtime PM resume path giving a kernel
splat like this if the device has no interrupts:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual
  address 00000001 when read&lt;/p&gt;
&lt;p&gt;PC is at bmc150_accel_set_interrupt+0x98/0x194
LR is at __pm_runtime_resume+0x5c/0x64
(...)
Call trace:
bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108
bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc
__iio_update_buffers from enable_store+0x84/0xc8
enable_store from kernfs_fop_write_iter+0x154/0x1b4&lt;/p&gt;
&lt;p&gt;This bug seems to have been in the driver since the beginning,
but it only manifests recently, I do not know why.&lt;/p&gt;
&lt;p&gt;Store the IRQ number in the state struct, as this is a common
pattern in other drivers, then use this to determine if we have
IRQ support or not.(CVE-2025-68330)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver&lt;/p&gt;
&lt;p&gt;at91_adc_interrupt can call at91_adc_touch_data_handler function
to start the work by schedule_work(&amp;amp;amp;st-&amp;amp;gt;touch_st.workq).&lt;/p&gt;
&lt;p&gt;If we remove the module which will call at91_adc_remove to
make cleanup, it will free indio_d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3155</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20416-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-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/opensuse-su-2026:20416-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0962-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0962-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:0962-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71199</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71199</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 204 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver at91_adc_interrupt can call at91_adc_touch_data_handler function to start the work by schedule_work(&amp;amp;st-&amp;gt;touch_st.workq). If we remove the module which will call at91_adc_remove to make cleanup, it will free indio_dev through iio_device_unregister but quite a bit later. While the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0                                      CPU1                                      | at91_adc_workq_handler at91_adc_remove                      | iio_device_unregister(indio_dev)     | //free indio_dev a bit later         |                                      | iio_push_to_buffers(indio_dev)                                      | //use indio_dev Fix it by ensuring that the work is canceled before proceeding with the cleanup in at91_adc_remove.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 204 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver at91_adc_interrupt can call at91_adc_touch_data_handler function to start the work by schedule_work(&amp;amp;st-&amp;gt;touch_st.workq). If we remove the module which will call at91_adc_remove to make cleanup, it will free indio_dev through iio_device_unregister but quite a bit later. While the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0                                      CPU1                                      | at91_adc_workq_handler at91_adc_remove                      | iio_device_unregister(indio_dev)     | //free indio_dev a bit later         |                                      | iio_push_to_buffers(indio_dev)                                      | //use indio_dev Fix it by ensuring that the work is canceled before proceeding with the cleanup in at91_adc_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71199</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0324 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0324</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0324</guid>
    </item>
  </channel>
</rss>
