<?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://127.0.0.1:10001</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, 21 Nov 2026 10:16:00 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2024-35957 — CVE-2024-35957 does not affect BellSoft software</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-35957</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2024-35957</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0611 — 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://127.0.0.1:10001/vuln/certfr-2024-avi-0611</link>
      <description>certfr-2024-avi-0611</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0611</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35957</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35957</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 74 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix WARN_ON in iommu probe path Commit 1a75cc710b95 (&amp;#34;iommu/vt-d: Use rbtree to track iommu probed devices&amp;#34;) adds all devices probed by the iommu driver in a rbtree indexed by the source ID of each device. It assumes that each device has a unique source ID. This assumption is incorrect and the VT-d spec doesn&amp;#39;t state this requirement either. The reason for using a rbtree to track devices is to look up the device with PCI bus and devfunc in the paths of handling ATS invalidation time out error and the PRI I/O page faults. Both are PCI ATS feature related. Only track the devices that have PCI ATS capabilities in the rbtree to avoid unnecessary WARN_ON in the iommu probe path. Otherwise, on some platforms below kernel splat will be displayed and the iommu probe results in failure.  WARNING: CPU: 3 PID: 166 at drivers/iommu/intel/iommu.c:158 intel_iommu_probe_device+0x319/0xd90  Call Trace:   &amp;lt;TASK&amp;gt;   ? __warn+0x7e/0x180   ? intel_iommu_probe_device+0x319/0xd90   ? report_bug+0x1f8/0x200   ? handle_bug+0x3c/0x70   ? exc_invalid_op+0x18/0x70   ? asm_exc_invalid_op+0x1a/0x20   ? intel_iommu_probe_device+0x319/0xd90   ? debug_mutex_init+0x37/0x50   __iommu_probe_device+0xf2/0x4f0   iommu_probe_device+0x22/0x70   iommu_bus_notifier+0x1e/0x40   notifier_call_chain+0x46/0x150   blocking_notifier_call_chain+0x42/0x60   bus_notify+0x2f/0x50   device_add+0x5ed/0x7e0   platform_device_add+0xf5/0x240   mfd_add_…&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 74 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix WARN_ON in iommu probe path Commit 1a75cc710b95 (&amp;#34;iommu/vt-d: Use rbtree to track iommu probed devices&amp;#34;) adds all devices probed by the iommu driver in a rbtree indexed by the source ID of each device. It assumes that each device has a unique source ID. This assumption is incorrect and the VT-d spec doesn&amp;#39;t state this requirement either. The reason for using a rbtree to track devices is to look up the device with PCI bus and devfunc in the paths of handling ATS invalidation time out error and the PRI I/O page faults. Both are PCI ATS feature related. Only track the devices that have PCI ATS capabilities in the rbtree to avoid unnecessary WARN_ON in the iommu probe path. Otherwise, on some platforms below kernel splat will be displayed and the iommu probe results in failure.  WARNING: CPU: 3 PID: 166 at drivers/iommu/intel/iommu.c:158 intel_iommu_probe_device+0x319/0xd90  Call Trace:   &amp;lt;TASK&amp;gt;   ? __warn+0x7e/0x180   ? intel_iommu_probe_device+0x319/0xd90   ? report_bug+0x1f8/0x200   ? handle_bug+0x3c/0x70   ? exc_invalid_op+0x18/0x70   ? asm_exc_invalid_op+0x1a/0x20   ? intel_iommu_probe_device+0x319/0xd90   ? debug_mutex_init+0x37/0x50   __iommu_probe_device+0xf2/0x4f0   iommu_probe_device+0x22/0x70   iommu_bus_notifier+0x1e/0x40   notifier_call_chain+0x46/0x150   blocking_notifier_call_chain+0x42/0x60   bus_notify+0x2f/0x50   device_add+0x5ed/0x7e0   platform_device_add+0xf5/0x240   mfd_add_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-35957</guid>
    </item>
  </channel>
</rss>
