<?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>Wed, 07 Oct 2026 11:13:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02462</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02462</link>
      <description>bdu:2026-02462</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02462</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37837</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37837</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-37837</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0559 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0559</link>
      <description>certfr-2025-avi-0559</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0559</guid>
    </item>
    <item>
      <title>EUVD-2026-314269</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314269</link>
      <description>EUVD-2026-314269</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314269</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37837</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37837</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent()&lt;/p&gt;
&lt;p&gt;Two WARNINGs are observed when SMMU driver rolls back upon failure:
 arm-smmu-v3.9.auto: Failed to register iommu
 arm-smmu-v3.9.auto: probe with driver arm-smmu-v3 failed with error -22
 ------------[ cut here ]------------
 WARNING: CPU: 5 PID: 1 at kernel/dma/mapping.c:74 dmam_free_coherent+0xc0/0xd8
 Call trace:
  dmam_free_coherent+0xc0/0xd8 (P)
  tegra241_vintf_free_lvcmdq+0x74/0x188
  tegra241_cmdqv_remove_vintf+0x60/0x148
  tegra241_cmdqv_remove+0x48/0xc8
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40
 ------------[ cut here ]------------
 128 pages are still in use!
 WARNING: CPU: 16 PID: 1 at mm/page_alloc.c:6902 free_contig_range+0x18c/0x1c8
 Call trace:
  free_contig_range+0x18c/0x1c8 (P)
  cma_release+0x154/0x2f0
  dma_free_contiguous+0x38/0xa0
  dma_direct_free+0x10c/0x248
  dma_free_attrs+0x100/0x290
  dmam_free_coherent+0x78/0xd8
  tegra241_vintf_free_lvcmdq+0x74/0x160
  tegra241_cmdqv_remove+0x98/0x198
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40&lt;/p&gt;
&lt;p&gt;This is because the LVCMDQ queue memory are managed by devres, while that
dmam_free_coherent() is called in the context of devm_action_release().&lt;/p&gt;
&lt;p&gt;Jason pointed out that &amp;#34;arm_smmu_impl_probe() has mis-ordered the devres
callbacks if ops-&amp;gt;device_remove() is going to be manually freeing things
that probe allocated&amp;#34;:
https://lore.kernel.org/linux-iom…&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/tegra241-cmdqv: Fix warnings due to dmam_free_coherent()&lt;/p&gt;
&lt;p&gt;Two WARNINGs are observed when SMMU driver rolls back upon failure:
 arm-smmu-v3.9.auto: Failed to register iommu
 arm-smmu-v3.9.auto: probe with driver arm-smmu-v3 failed with error -22
 ------------[ cut here ]------------
 WARNING: CPU: 5 PID: 1 at kernel/dma/mapping.c:74 dmam_free_coherent+0xc0/0xd8
 Call trace:
  dmam_free_coherent+0xc0/0xd8 (P)
  tegra241_vintf_free_lvcmdq+0x74/0x188
  tegra241_cmdqv_remove_vintf+0x60/0x148
  tegra241_cmdqv_remove+0x48/0xc8
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40
 ------------[ cut here ]------------
 128 pages are still in use!
 WARNING: CPU: 16 PID: 1 at mm/page_alloc.c:6902 free_contig_range+0x18c/0x1c8
 Call trace:
  free_contig_range+0x18c/0x1c8 (P)
  cma_release+0x154/0x2f0
  dma_free_contiguous+0x38/0xa0
  dma_direct_free+0x10c/0x248
  dma_free_attrs+0x100/0x290
  dmam_free_coherent+0x78/0xd8
  tegra241_vintf_free_lvcmdq+0x74/0x160
  tegra241_cmdqv_remove+0x98/0x198
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40&lt;/p&gt;
&lt;p&gt;This is because the LVCMDQ queue memory are managed by devres, while that
dmam_free_coherent() is called in the context of devm_action_release().&lt;/p&gt;
&lt;p&gt;Jason pointed out that &amp;#34;arm_smmu_impl_probe() has mis-ordered the devres
callbacks if ops-&amp;gt;device_remove() is going to be manually freeing things
that probe allocated&amp;#34;:
https://lore.kernel.org/linux-iom…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37837</guid>
    </item>
    <item>
      <title>GHSA-q7q8-5x36-4r88</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q7q8-5x36-4r88</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent()&lt;/p&gt;
&lt;p&gt;Two WARNINGs are observed when SMMU driver rolls back upon failure:
 arm-smmu-v3.9.auto: Failed to register iommu
 arm-smmu-v3.9.auto: probe with driver arm-smmu-v3 failed with error -22
 ------------[ cut here ]------------
 WARNING: CPU: 5 PID: 1 at kernel/dma/mapping.c:74 dmam_free_coherent+0xc0/0xd8
 Call trace:
  dmam_free_coherent+0xc0/0xd8 (P)
  tegra241_vintf_free_lvcmdq+0x74/0x188
  tegra241_cmdqv_remove_vintf+0x60/0x148
  tegra241_cmdqv_remove+0x48/0xc8
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40
 ------------[ cut here ]------------
 128 pages are still in use!
 WARNING: CPU: 16 PID: 1 at mm/page_alloc.c:6902 free_contig_range+0x18c/0x1c8
 Call trace:
  free_contig_range+0x18c/0x1c8 (P)
  cma_release+0x154/0x2f0
  dma_free_contiguous+0x38/0xa0
  dma_direct_free+0x10c/0x248
  dma_free_attrs+0x100/0x290
  dmam_free_coherent+0x78/0xd8
  tegra241_vintf_free_lvcmdq+0x74/0x160
  tegra241_cmdqv_remove+0x98/0x198
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40&lt;/p&gt;
&lt;p&gt;This is because the LVCMDQ queue memory are managed by devres, while that
dmam_free_coherent() is called in the context of devm_action_release().&lt;/p&gt;
&lt;p&gt;Jason pointed out that &amp;#34;arm_smmu_impl_probe() has mis-ordered the devres
callbacks if ops-&amp;gt;device_remove() is going to be manually freeing things
that probe allocated&amp;#34;:
https://lore.kernel.org/linux-iom…&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/tegra241-cmdqv: Fix warnings due to dmam_free_coherent()&lt;/p&gt;
&lt;p&gt;Two WARNINGs are observed when SMMU driver rolls back upon failure:
 arm-smmu-v3.9.auto: Failed to register iommu
 arm-smmu-v3.9.auto: probe with driver arm-smmu-v3 failed with error -22
 ------------[ cut here ]------------
 WARNING: CPU: 5 PID: 1 at kernel/dma/mapping.c:74 dmam_free_coherent+0xc0/0xd8
 Call trace:
  dmam_free_coherent+0xc0/0xd8 (P)
  tegra241_vintf_free_lvcmdq+0x74/0x188
  tegra241_cmdqv_remove_vintf+0x60/0x148
  tegra241_cmdqv_remove+0x48/0xc8
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40
 ------------[ cut here ]------------
 128 pages are still in use!
 WARNING: CPU: 16 PID: 1 at mm/page_alloc.c:6902 free_contig_range+0x18c/0x1c8
 Call trace:
  free_contig_range+0x18c/0x1c8 (P)
  cma_release+0x154/0x2f0
  dma_free_contiguous+0x38/0xa0
  dma_direct_free+0x10c/0x248
  dma_free_attrs+0x100/0x290
  dmam_free_coherent+0x78/0xd8
  tegra241_vintf_free_lvcmdq+0x74/0x160
  tegra241_cmdqv_remove+0x98/0x198
  arm_smmu_impl_remove+0x28/0x60
  devm_action_release+0x1c/0x40&lt;/p&gt;
&lt;p&gt;This is because the LVCMDQ queue memory are managed by devres, while that
dmam_free_coherent() is called in the context of devm_action_release().&lt;/p&gt;
&lt;p&gt;Jason pointed out that &amp;#34;arm_smmu_impl_probe() has mis-ordered the devres
callbacks if ops-&amp;gt;device_remove() is going to be manually freeing things
that probe allocated&amp;#34;:
https://lore.kernel.org/linux-iom…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q7q8-5x36-4r88</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02333-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02333-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:02333-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37837</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37837</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 76 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent() Two WARNINGs are observed when SMMU driver rolls back upon failure:  arm-smmu-v3.9.auto: Failed to register iommu  arm-smmu-v3.9.auto: probe with driver arm-smmu-v3 failed with error -22  ------------[ cut here ]------------  WARNING: CPU: 5 PID: 1 at kernel/dma/mapping.c:74 dmam_free_coherent+0xc0/0xd8  Call trace:   dmam_free_coherent+0xc0/0xd8 (P)   tegra241_vintf_free_lvcmdq+0x74/0x188   tegra241_cmdqv_remove_vintf+0x60/0x148   tegra241_cmdqv_remove+0x48/0xc8   arm_smmu_impl_remove+0x28/0x60   devm_action_release+0x1c/0x40  ------------[ cut here ]------------  128 pages are still in use!  WARNING: CPU: 16 PID: 1 at mm/page_alloc.c:6902 free_contig_range+0x18c/0x1c8  Call trace:   free_contig_range+0x18c/0x1c8 (P)   cma_release+0x154/0x2f0   dma_free_contiguous+0x38/0xa0   dma_direct_free+0x10c/0x248   dma_free_attrs+0x100/0x290   dmam_free_coherent+0x78/0xd8   tegra241_vintf_free_lvcmdq+0x74/0x160   tegra241_cmdqv_remove+0x98/0x198   arm_smmu_impl_remove+0x28/0x60   devm_action_release+0x1c/0x40 This is because the LVCMDQ queue memory are managed by devres, while that dmam_free_coherent() is called in the context of devm_action_release(). Jason pointed out that &amp;#34;arm_smmu_impl_probe() has mis-ordered the devres callbacks if ops-&amp;gt;device_remove() is going to be manually freeing things that probe allocated&amp;#34;: https://lore.kernel.org/linux-iommu/2…&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 76 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent() Two WARNINGs are observed when SMMU driver rolls back upon failure:  arm-smmu-v3.9.auto: Failed to register iommu  arm-smmu-v3.9.auto: probe with driver arm-smmu-v3 failed with error -22  ------------[ cut here ]------------  WARNING: CPU: 5 PID: 1 at kernel/dma/mapping.c:74 dmam_free_coherent+0xc0/0xd8  Call trace:   dmam_free_coherent+0xc0/0xd8 (P)   tegra241_vintf_free_lvcmdq+0x74/0x188   tegra241_cmdqv_remove_vintf+0x60/0x148   tegra241_cmdqv_remove+0x48/0xc8   arm_smmu_impl_remove+0x28/0x60   devm_action_release+0x1c/0x40  ------------[ cut here ]------------  128 pages are still in use!  WARNING: CPU: 16 PID: 1 at mm/page_alloc.c:6902 free_contig_range+0x18c/0x1c8  Call trace:   free_contig_range+0x18c/0x1c8 (P)   cma_release+0x154/0x2f0   dma_free_contiguous+0x38/0xa0   dma_direct_free+0x10c/0x248   dma_free_attrs+0x100/0x290   dmam_free_coherent+0x78/0xd8   tegra241_vintf_free_lvcmdq+0x74/0x160   tegra241_cmdqv_remove+0x98/0x198   arm_smmu_impl_remove+0x28/0x60   devm_action_release+0x1c/0x40 This is because the LVCMDQ queue memory are managed by devres, while that dmam_free_coherent() is called in the context of devm_action_release(). Jason pointed out that &amp;#34;arm_smmu_impl_probe() has mis-ordered the devres callbacks if ops-&amp;gt;device_remove() is going to be manually freeing things that probe allocated&amp;#34;: https://lore.kernel.org/linux-iommu/2…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37837</guid>
    </item>
  </channel>
</rss>
