<?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 16:23:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89449</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89449</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-89449</guid>
    </item>
    <item>
      <title>EUVD-2026-366993</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-366993</link>
      <description>EUVD-2026-366993</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-366993</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89449</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89449</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add&lt;/p&gt;
&lt;p&gt;iommu_mock_device_add() first calls iommu_fwspec_init(), which on
success allocates both dev-&amp;gt;iommu (via dev_iommu_get()) and
dev-&amp;gt;iommu-&amp;gt;fwspec. If the subsequent device_add(dev) call fails,
the error path only calls iommu_fwspec_free(dev), which frees
fwspec but leaves dev-&amp;gt;iommu still allocated.&lt;/p&gt;
&lt;p&gt;This triggers the following kmemleak report when fuzzing with Syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff888011e0a200 (size 192):
  comm &amp;#34;syz.1.1695&amp;#34;, pid 24885, jiffies 4295222527
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..
    ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................
  backtrace (crc 25df5bb3):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4575 [inline]
    slab_alloc_node mm/slub.c:4899 [inline]
    __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415
    kmalloc_noprof include/linux/slab.h:950 [inline]
    kzalloc_noprof include/linux/slab.h:1188 [inline]
    dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408
    iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087
    iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385
    mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]
    iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]
    iommufd_test…&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: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add&lt;/p&gt;
&lt;p&gt;iommu_mock_device_add() first calls iommu_fwspec_init(), which on
success allocates both dev-&amp;gt;iommu (via dev_iommu_get()) and
dev-&amp;gt;iommu-&amp;gt;fwspec. If the subsequent device_add(dev) call fails,
the error path only calls iommu_fwspec_free(dev), which frees
fwspec but leaves dev-&amp;gt;iommu still allocated.&lt;/p&gt;
&lt;p&gt;This triggers the following kmemleak report when fuzzing with Syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff888011e0a200 (size 192):
  comm &amp;#34;syz.1.1695&amp;#34;, pid 24885, jiffies 4295222527
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..
    ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................
  backtrace (crc 25df5bb3):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4575 [inline]
    slab_alloc_node mm/slub.c:4899 [inline]
    __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415
    kmalloc_noprof include/linux/slab.h:950 [inline]
    kzalloc_noprof include/linux/slab.h:1188 [inline]
    dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408
    iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087
    iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385
    mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]
    iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]
    iommufd_test…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89449</guid>
    </item>
    <item>
      <title>GHSA-3365-g9v5-8jg9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3365-g9v5-8jg9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add&lt;/p&gt;
&lt;p&gt;iommu_mock_device_add() first calls iommu_fwspec_init(), which on
success allocates both dev-&amp;gt;iommu (via dev_iommu_get()) and
dev-&amp;gt;iommu-&amp;gt;fwspec. If the subsequent device_add(dev) call fails,
the error path only calls iommu_fwspec_free(dev), which frees
fwspec but leaves dev-&amp;gt;iommu still allocated.&lt;/p&gt;
&lt;p&gt;This triggers the following kmemleak report when fuzzing with Syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff888011e0a200 (size 192):
  comm &amp;#34;syz.1.1695&amp;#34;, pid 24885, jiffies 4295222527
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..
    ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................
  backtrace (crc 25df5bb3):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4575 [inline]
    slab_alloc_node mm/slub.c:4899 [inline]
    __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415
    kmalloc_noprof include/linux/slab.h:950 [inline]
    kzalloc_noprof include/linux/slab.h:1188 [inline]
    dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408
    iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087
    iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385
    mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]
    iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]
    iommufd_test…&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: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add&lt;/p&gt;
&lt;p&gt;iommu_mock_device_add() first calls iommu_fwspec_init(), which on
success allocates both dev-&amp;gt;iommu (via dev_iommu_get()) and
dev-&amp;gt;iommu-&amp;gt;fwspec. If the subsequent device_add(dev) call fails,
the error path only calls iommu_fwspec_free(dev), which frees
fwspec but leaves dev-&amp;gt;iommu still allocated.&lt;/p&gt;
&lt;p&gt;This triggers the following kmemleak report when fuzzing with Syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff888011e0a200 (size 192):
  comm &amp;#34;syz.1.1695&amp;#34;, pid 24885, jiffies 4295222527
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..
    ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................
  backtrace (crc 25df5bb3):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4575 [inline]
    slab_alloc_node mm/slub.c:4899 [inline]
    __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415
    kmalloc_noprof include/linux/slab.h:950 [inline]
    kzalloc_noprof include/linux/slab.h:1188 [inline]
    dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408
    iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087
    iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385
    mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]
    iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]
    iommufd_test…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3365-g9v5-8jg9</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89449</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89449</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add iommu_mock_device_add() first calls iommu_fwspec_init(), which on success allocates both dev-&amp;gt;iommu (via dev_iommu_get()) and dev-&amp;gt;iommu-&amp;gt;fwspec. If the subsequent device_add(dev) call fails, the error path only calls iommu_fwspec_free(dev), which frees fwspec but leaves dev-&amp;gt;iommu still allocated. This triggers the following kmemleak report when fuzzing with Syzkaller: BUG: memory leak unreferenced object 0xffff888011e0a200 (size 192):   comm &amp;#34;syz.1.1695&amp;#34;, pid 24885, jiffies 4295222527   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..     ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................   backtrace (crc 25df5bb3):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4575 [inline]     slab_alloc_node mm/slub.c:4899 [inline]     __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415     kmalloc_noprof include/linux/slab.h:950 [inline]     kzalloc_noprof include/linux/slab.h:1188 [inline]     dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408     iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087     iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385     mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]     iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]     iommufd_test+0x2…&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add iommu_mock_device_add() first calls iommu_fwspec_init(), which on success allocates both dev-&amp;gt;iommu (via dev_iommu_get()) and dev-&amp;gt;iommu-&amp;gt;fwspec. If the subsequent device_add(dev) call fails, the error path only calls iommu_fwspec_free(dev), which frees fwspec but leaves dev-&amp;gt;iommu still allocated. This triggers the following kmemleak report when fuzzing with Syzkaller: BUG: memory leak unreferenced object 0xffff888011e0a200 (size 192):   comm &amp;#34;syz.1.1695&amp;#34;, pid 24885, jiffies 4295222527   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..     ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................   backtrace (crc 25df5bb3):     kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]     slab_post_alloc_hook mm/slub.c:4575 [inline]     slab_alloc_node mm/slub.c:4899 [inline]     __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415     kmalloc_noprof include/linux/slab.h:950 [inline]     kzalloc_noprof include/linux/slab.h:1188 [inline]     dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408     iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087     iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385     mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]     iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]     iommufd_test+0x2…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89449</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
