<?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 06:10:40 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06062</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06062</link>
      <description>bdu:2025-06062</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06062</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-310331</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310331</link>
      <description>EUVD-2026-310331</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310331</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49083</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49083</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/omap: Fix regression in probe for NULL pointer dereference&lt;/p&gt;
&lt;p&gt;Commit 3f6634d997db (&amp;#34;iommu: Use right way to retrieve iommu_ops&amp;#34;) started
triggering a NULL pointer dereference for some omap variants:&lt;/p&gt;
&lt;p&gt;__iommu_probe_device from probe_iommu_group+0x2c/0x38
probe_iommu_group from bus_for_each_dev+0x74/0xbc
bus_for_each_dev from bus_iommu_probe+0x34/0x2e8
bus_iommu_probe from bus_set_iommu+0x80/0xc8
bus_set_iommu from omap_iommu_init+0x88/0xcc
omap_iommu_init from do_one_initcall+0x44/0x24&lt;/p&gt;
&lt;p&gt;This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV)
as noted by Jason Gunthorpe &amp;lt;jgg@ziepe.ca&amp;gt;.&lt;/p&gt;
&lt;p&gt;Looks like the regression already happened with an earlier commit
6785eb9105e3 (&amp;#34;iommu/omap: Convert to probe/release_device() call-backs&amp;#34;)
that changed the function return type and missed converting one place.&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/omap: Fix regression in probe for NULL pointer dereference&lt;/p&gt;
&lt;p&gt;Commit 3f6634d997db (&amp;#34;iommu: Use right way to retrieve iommu_ops&amp;#34;) started
triggering a NULL pointer dereference for some omap variants:&lt;/p&gt;
&lt;p&gt;__iommu_probe_device from probe_iommu_group+0x2c/0x38
probe_iommu_group from bus_for_each_dev+0x74/0xbc
bus_for_each_dev from bus_iommu_probe+0x34/0x2e8
bus_iommu_probe from bus_set_iommu+0x80/0xc8
bus_set_iommu from omap_iommu_init+0x88/0xcc
omap_iommu_init from do_one_initcall+0x44/0x24&lt;/p&gt;
&lt;p&gt;This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV)
as noted by Jason Gunthorpe &amp;lt;jgg@ziepe.ca&amp;gt;.&lt;/p&gt;
&lt;p&gt;Looks like the regression already happened with an earlier commit
6785eb9105e3 (&amp;#34;iommu/omap: Convert to probe/release_device() call-backs&amp;#34;)
that changed the function return type and missed converting one place.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49083</guid>
    </item>
    <item>
      <title>GHSA-3742-9rpq-whr7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3742-9rpq-whr7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/omap: Fix regression in probe for NULL pointer dereference&lt;/p&gt;
&lt;p&gt;Commit 3f6634d997db (&amp;#34;iommu: Use right way to retrieve iommu_ops&amp;#34;) started
triggering a NULL pointer dereference for some omap variants:&lt;/p&gt;
&lt;p&gt;__iommu_probe_device from probe_iommu_group+0x2c/0x38
probe_iommu_group from bus_for_each_dev+0x74/0xbc
bus_for_each_dev from bus_iommu_probe+0x34/0x2e8
bus_iommu_probe from bus_set_iommu+0x80/0xc8
bus_set_iommu from omap_iommu_init+0x88/0xcc
omap_iommu_init from do_one_initcall+0x44/0x24&lt;/p&gt;
&lt;p&gt;This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV)
as noted by Jason Gunthorpe &amp;lt;jgg@ziepe.ca&amp;gt;.&lt;/p&gt;
&lt;p&gt;Looks like the regression already happened with an earlier commit
6785eb9105e3 (&amp;#34;iommu/omap: Convert to probe/release_device() call-backs&amp;#34;)
that changed the function return type and missed converting one place.&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/omap: Fix regression in probe for NULL pointer dereference&lt;/p&gt;
&lt;p&gt;Commit 3f6634d997db (&amp;#34;iommu: Use right way to retrieve iommu_ops&amp;#34;) started
triggering a NULL pointer dereference for some omap variants:&lt;/p&gt;
&lt;p&gt;__iommu_probe_device from probe_iommu_group+0x2c/0x38
probe_iommu_group from bus_for_each_dev+0x74/0xbc
bus_for_each_dev from bus_iommu_probe+0x34/0x2e8
bus_iommu_probe from bus_set_iommu+0x80/0xc8
bus_set_iommu from omap_iommu_init+0x88/0xcc
omap_iommu_init from do_one_initcall+0x44/0x24&lt;/p&gt;
&lt;p&gt;This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV)
as noted by Jason Gunthorpe &amp;lt;jgg@ziepe.ca&amp;gt;.&lt;/p&gt;
&lt;p&gt;Looks like the regression already happened with an earlier commit
6785eb9105e3 (&amp;#34;iommu/omap: Convert to probe/release_device() call-backs&amp;#34;)
that changed the function return type and missed converting one place.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3742-9rpq-whr7</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-49083</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49083</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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/omap: Fix regression in probe for NULL pointer dereference Commit 3f6634d997db (&amp;#34;iommu: Use right way to retrieve iommu_ops&amp;#34;) started triggering a NULL pointer dereference for some omap variants: __iommu_probe_device from probe_iommu_group+0x2c/0x38 probe_iommu_group from bus_for_each_dev+0x74/0xbc bus_for_each_dev from bus_iommu_probe+0x34/0x2e8 bus_iommu_probe from bus_set_iommu+0x80/0xc8 bus_set_iommu from omap_iommu_init+0x88/0xcc omap_iommu_init from do_one_initcall+0x44/0x24 This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV) as noted by Jason Gunthorpe &amp;lt;jgg@ziepe.ca&amp;gt;. Looks like the regression already happened with an earlier commit 6785eb9105e3 (&amp;#34;iommu/omap: Convert to probe/release_device() call-backs&amp;#34;) that changed the function return type and missed converting one place.&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 85 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/omap: Fix regression in probe for NULL pointer dereference Commit 3f6634d997db (&amp;#34;iommu: Use right way to retrieve iommu_ops&amp;#34;) started triggering a NULL pointer dereference for some omap variants: __iommu_probe_device from probe_iommu_group+0x2c/0x38 probe_iommu_group from bus_for_each_dev+0x74/0xbc bus_for_each_dev from bus_iommu_probe+0x34/0x2e8 bus_iommu_probe from bus_set_iommu+0x80/0xc8 bus_set_iommu from omap_iommu_init+0x88/0xcc omap_iommu_init from do_one_initcall+0x44/0x24 This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV) as noted by Jason Gunthorpe &amp;lt;jgg@ziepe.ca&amp;gt;. Looks like the regression already happened with an earlier commit 6785eb9105e3 (&amp;#34;iommu/omap: Convert to probe/release_device() call-backs&amp;#34;) that changed the function return type and missed converting one place.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49083</guid>
    </item>
  </channel>
</rss>
