<?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>Mon, 05 Oct 2026 15:05:48 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03680</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03680</link>
      <description>bdu:2026-03680</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03680</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-320301</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320301</link>
      <description>EUVD-2026-320301</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320301</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49427</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49427</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/mediatek: Remove clk_disable in mtk_iommu_remove&lt;/p&gt;
&lt;p&gt;After the commit b34ea31fe013 (&amp;#34;iommu/mediatek: Always enable the clk on
resume&amp;#34;), the iommu clock is controlled by the runtime callback.
thus remove the clk control in the mtk_iommu_remove.&lt;/p&gt;
&lt;p&gt;Otherwise, it will warning like:&lt;/p&gt;
&lt;p&gt;echo 14018000.iommu &amp;gt; /sys/bus/platform/drivers/mtk-iommu/unbind&lt;/p&gt;
&lt;p&gt;[   51.413044] ------------[ cut here ]------------
[   51.413648] vpp0_smi_iommu already disabled
[   51.414233] WARNING: CPU: 2 PID: 157 at */v5.15-rc1/kernel/mediatek/
                          drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8
[   51.417174] Hardware name: MT8195V/C(ENG) (DT)
[   51.418635] pc : clk_core_disable+0xb0/0xb8
[   51.419177] lr : clk_core_disable+0xb0/0xb8
...
[   51.429375] Call trace:
[   51.429694]  clk_core_disable+0xb0/0xb8
[   51.430193]  clk_core_disable_lock+0x24/0x40
[   51.430745]  clk_disable+0x20/0x30
[   51.431189]  mtk_iommu_remove+0x58/0x118
[   51.431705]  platform_remove+0x28/0x60
[   51.432197]  device_release_driver_internal+0x110/0x1f0
[   51.432873]  device_driver_detach+0x18/0x28
[   51.433418]  unbind_store+0xd4/0x108
[   51.433886]  drv_attr_store+0x24/0x38
[   51.434363]  sysfs_kf_write+0x40/0x58
[   51.434843]  kernfs_fop_write_iter+0x164/0x1e0&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;iommu/mediatek: Remove clk_disable in mtk_iommu_remove&lt;/p&gt;
&lt;p&gt;After the commit b34ea31fe013 (&amp;#34;iommu/mediatek: Always enable the clk on
resume&amp;#34;), the iommu clock is controlled by the runtime callback.
thus remove the clk control in the mtk_iommu_remove.&lt;/p&gt;
&lt;p&gt;Otherwise, it will warning like:&lt;/p&gt;
&lt;p&gt;echo 14018000.iommu &amp;gt; /sys/bus/platform/drivers/mtk-iommu/unbind&lt;/p&gt;
&lt;p&gt;[   51.413044] ------------[ cut here ]------------
[   51.413648] vpp0_smi_iommu already disabled
[   51.414233] WARNING: CPU: 2 PID: 157 at */v5.15-rc1/kernel/mediatek/
                          drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8
[   51.417174] Hardware name: MT8195V/C(ENG) (DT)
[   51.418635] pc : clk_core_disable+0xb0/0xb8
[   51.419177] lr : clk_core_disable+0xb0/0xb8
...
[   51.429375] Call trace:
[   51.429694]  clk_core_disable+0xb0/0xb8
[   51.430193]  clk_core_disable_lock+0x24/0x40
[   51.430745]  clk_disable+0x20/0x30
[   51.431189]  mtk_iommu_remove+0x58/0x118
[   51.431705]  platform_remove+0x28/0x60
[   51.432197]  device_release_driver_internal+0x110/0x1f0
[   51.432873]  device_driver_detach+0x18/0x28
[   51.433418]  unbind_store+0xd4/0x108
[   51.433886]  drv_attr_store+0x24/0x38
[   51.434363]  sysfs_kf_write+0x40/0x58
[   51.434843]  kernfs_fop_write_iter+0x164/0x1e0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49427</guid>
    </item>
    <item>
      <title>GHSA-q88h-gvfq-84pc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q88h-gvfq-84pc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/mediatek: Remove clk_disable in mtk_iommu_remove&lt;/p&gt;
&lt;p&gt;After the commit b34ea31fe013 (&amp;#34;iommu/mediatek: Always enable the clk on
resume&amp;#34;), the iommu clock is controlled by the runtime callback.
thus remove the clk control in the mtk_iommu_remove.&lt;/p&gt;
&lt;p&gt;Otherwise, it will warning like:&lt;/p&gt;
&lt;p&gt;echo 14018000.iommu &amp;gt; /sys/bus/platform/drivers/mtk-iommu/unbind&lt;/p&gt;
&lt;p&gt;[   51.413044] ------------[ cut here ]------------
[   51.413648] vpp0_smi_iommu already disabled
[   51.414233] WARNING: CPU: 2 PID: 157 at */v5.15-rc1/kernel/mediatek/
                          drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8
[   51.417174] Hardware name: MT8195V/C(ENG) (DT)
[   51.418635] pc : clk_core_disable+0xb0/0xb8
[   51.419177] lr : clk_core_disable+0xb0/0xb8
...
[   51.429375] Call trace:
[   51.429694]  clk_core_disable+0xb0/0xb8
[   51.430193]  clk_core_disable_lock+0x24/0x40
[   51.430745]  clk_disable+0x20/0x30
[   51.431189]  mtk_iommu_remove+0x58/0x118
[   51.431705]  platform_remove+0x28/0x60
[   51.432197]  device_release_driver_internal+0x110/0x1f0
[   51.432873]  device_driver_detach+0x18/0x28
[   51.433418]  unbind_store+0xd4/0x108
[   51.433886]  drv_attr_store+0x24/0x38
[   51.434363]  sysfs_kf_write+0x40/0x58
[   51.434843]  kernfs_fop_write_iter+0x164/0x1e0&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;iommu/mediatek: Remove clk_disable in mtk_iommu_remove&lt;/p&gt;
&lt;p&gt;After the commit b34ea31fe013 (&amp;#34;iommu/mediatek: Always enable the clk on
resume&amp;#34;), the iommu clock is controlled by the runtime callback.
thus remove the clk control in the mtk_iommu_remove.&lt;/p&gt;
&lt;p&gt;Otherwise, it will warning like:&lt;/p&gt;
&lt;p&gt;echo 14018000.iommu &amp;gt; /sys/bus/platform/drivers/mtk-iommu/unbind&lt;/p&gt;
&lt;p&gt;[   51.413044] ------------[ cut here ]------------
[   51.413648] vpp0_smi_iommu already disabled
[   51.414233] WARNING: CPU: 2 PID: 157 at */v5.15-rc1/kernel/mediatek/
                          drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8
[   51.417174] Hardware name: MT8195V/C(ENG) (DT)
[   51.418635] pc : clk_core_disable+0xb0/0xb8
[   51.419177] lr : clk_core_disable+0xb0/0xb8
...
[   51.429375] Call trace:
[   51.429694]  clk_core_disable+0xb0/0xb8
[   51.430193]  clk_core_disable_lock+0x24/0x40
[   51.430745]  clk_disable+0x20/0x30
[   51.431189]  mtk_iommu_remove+0x58/0x118
[   51.431705]  platform_remove+0x28/0x60
[   51.432197]  device_release_driver_internal+0x110/0x1f0
[   51.432873]  device_driver_detach+0x18/0x28
[   51.433418]  unbind_store+0xd4/0x108
[   51.433886]  drv_attr_store+0x24/0x38
[   51.434363]  sysfs_kf_write+0x40/0x58
[   51.434843]  kernfs_fop_write_iter+0x164/0x1e0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q88h-gvfq-84pc</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-49427</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49427</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Remove clk_disable in mtk_iommu_remove After the commit b34ea31fe013 (&amp;#34;iommu/mediatek: Always enable the clk on resume&amp;#34;), the iommu clock is controlled by the runtime callback. thus remove the clk control in the mtk_iommu_remove. Otherwise, it will warning like: echo 14018000.iommu &amp;gt; /sys/bus/platform/drivers/mtk-iommu/unbind [   51.413044] ------------[ cut here ]------------ [   51.413648] vpp0_smi_iommu already disabled [   51.414233] WARNING: CPU: 2 PID: 157 at */v5.15-rc1/kernel/mediatek/                           drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8 [   51.417174] Hardware name: MT8195V/C(ENG) (DT) [   51.418635] pc : clk_core_disable+0xb0/0xb8 [   51.419177] lr : clk_core_disable+0xb0/0xb8 ... [   51.429375] Call trace: [   51.429694]  clk_core_disable+0xb0/0xb8 [   51.430193]  clk_core_disable_lock+0x24/0x40 [   51.430745]  clk_disable+0x20/0x30 [   51.431189]  mtk_iommu_remove+0x58/0x118 [   51.431705]  platform_remove+0x28/0x60 [   51.432197]  device_release_driver_internal+0x110/0x1f0 [   51.432873]  device_driver_detach+0x18/0x28 [   51.433418]  unbind_store+0xd4/0x108 [   51.433886]  drv_attr_store+0x24/0x38 [   51.434363]  sysfs_kf_write+0x40/0x58 [   51.434843]  kernfs_fop_write_iter+0x164/0x1e0&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 91 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Remove clk_disable in mtk_iommu_remove After the commit b34ea31fe013 (&amp;#34;iommu/mediatek: Always enable the clk on resume&amp;#34;), the iommu clock is controlled by the runtime callback. thus remove the clk control in the mtk_iommu_remove. Otherwise, it will warning like: echo 14018000.iommu &amp;gt; /sys/bus/platform/drivers/mtk-iommu/unbind [   51.413044] ------------[ cut here ]------------ [   51.413648] vpp0_smi_iommu already disabled [   51.414233] WARNING: CPU: 2 PID: 157 at */v5.15-rc1/kernel/mediatek/                           drivers/clk/clk.c:952 clk_core_disable+0xb0/0xb8 [   51.417174] Hardware name: MT8195V/C(ENG) (DT) [   51.418635] pc : clk_core_disable+0xb0/0xb8 [   51.419177] lr : clk_core_disable+0xb0/0xb8 ... [   51.429375] Call trace: [   51.429694]  clk_core_disable+0xb0/0xb8 [   51.430193]  clk_core_disable_lock+0x24/0x40 [   51.430745]  clk_disable+0x20/0x30 [   51.431189]  mtk_iommu_remove+0x58/0x118 [   51.431705]  platform_remove+0x28/0x60 [   51.432197]  device_release_driver_internal+0x110/0x1f0 [   51.432873]  device_driver_detach+0x18/0x28 [   51.433418]  unbind_store+0xd4/0x108 [   51.433886]  drv_attr_store+0x24/0x38 [   51.434363]  sysfs_kf_write+0x40/0x58 [   51.434843]  kernfs_fop_write_iter+0x164/0x1e0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49427</guid>
    </item>
  </channel>
</rss>
