<?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 16:31:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21876</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21876</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://127.0.0.1:10001/vuln/bell-cve-2025-21876</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0307 — 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://127.0.0.1:10001/vuln/certfr-2025-avi-0307</link>
      <description>certfr-2025-avi-0307</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0307</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21876</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21876</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/vt-d: Fix suspicious RCU usage Commit &amp;lt;d74169ceb0d2&amp;gt; (&amp;#34;iommu/vt-d: Allocate DMAR fault interrupts locally&amp;#34;) moved the call to enable_drhd_fault_handling() to a code path that does not hold any lock while traversing the drhd list. Fix it by ensuring the dmar_global_lock lock is held when traversing the drhd list. Without this fix, the following warning is triggered:  =============================  WARNING: suspicious RCU usage  6.14.0-rc3 #55 Not tainted  -----------------------------  drivers/iommu/intel/dmar.c:2046 RCU-list traversed in non-reader section!!                other info that might help us debug this:                rcu_scheduler_active = 1, debug_locks = 1  2 locks held by cpuhp/1/23:  #0: ffffffff84a67c50 (cpu_hotplug_lock){++++}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0  #1: ffffffff84a6a380 (cpuhp_state-up){+.+.}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0  stack backtrace:  CPU: 1 UID: 0 PID: 23 Comm: cpuhp/1 Not tainted 6.14.0-rc3 #55  Call Trace:   &amp;lt;TASK&amp;gt;   dump_stack_lvl+0xb7/0xd0   lockdep_rcu_suspicious+0x159/0x1f0   ? __pfx_enable_drhd_fault_handling+0x10/0x10   enable_drhd_fault_handling+0x151/0x180   cpuhp_invoke_callback+0x1df/0x990   cpuhp_thread_fun+0x1ea/0x2c0   smpboot_thread_fn+0x1f5/0x2e0   ? __pfx_smpboot_thread_fn+0x10/0x10   kthread+0x12a/0x2d0   ? __pfx_kthread+0x10/0x10   ret_from_fork+0x4a/0x60   ? __pfx_kthread+0x10/0x10   ret_from_fork_asm+0x1a/0x30   &amp;lt;/TASK&amp;gt; Holding th…&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/vt-d: Fix suspicious RCU usage Commit &amp;lt;d74169ceb0d2&amp;gt; (&amp;#34;iommu/vt-d: Allocate DMAR fault interrupts locally&amp;#34;) moved the call to enable_drhd_fault_handling() to a code path that does not hold any lock while traversing the drhd list. Fix it by ensuring the dmar_global_lock lock is held when traversing the drhd list. Without this fix, the following warning is triggered:  =============================  WARNING: suspicious RCU usage  6.14.0-rc3 #55 Not tainted  -----------------------------  drivers/iommu/intel/dmar.c:2046 RCU-list traversed in non-reader section!!                other info that might help us debug this:                rcu_scheduler_active = 1, debug_locks = 1  2 locks held by cpuhp/1/23:  #0: ffffffff84a67c50 (cpu_hotplug_lock){++++}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0  #1: ffffffff84a6a380 (cpuhp_state-up){+.+.}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0  stack backtrace:  CPU: 1 UID: 0 PID: 23 Comm: cpuhp/1 Not tainted 6.14.0-rc3 #55  Call Trace:   &amp;lt;TASK&amp;gt;   dump_stack_lvl+0xb7/0xd0   lockdep_rcu_suspicious+0x159/0x1f0   ? __pfx_enable_drhd_fault_handling+0x10/0x10   enable_drhd_fault_handling+0x151/0x180   cpuhp_invoke_callback+0x1df/0x990   cpuhp_thread_fun+0x1ea/0x2c0   smpboot_thread_fn+0x1f5/0x2e0   ? __pfx_smpboot_thread_fn+0x10/0x10   kthread+0x12a/0x2d0   ? __pfx_kthread+0x10/0x10   ret_from_fork+0x4a/0x60   ? __pfx_kthread+0x10/0x10   ret_from_fork_asm+0x1a/0x30   &amp;lt;/TASK&amp;gt; Holding th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21876</guid>
    </item>
  </channel>
</rss>
