<?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 13:07:07 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-68347 — CVE-2026-68347 does not affect BellSoft software</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-68347</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-2026-68347</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1286 — 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-2026-avi-1286</link>
      <description>certfr-2026-avi-1286</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1286</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-68347</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68347</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 114 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix IRQ unsafe locking in gdom allocation Lockdep complains:   [  259.410489] =====================================================   [  259.417287] WARNING: HARDIRQ-safe -&amp;gt; HARDIRQ-unsafe lock order detected   [  259.424667] 7.0.0-g51db1d8d2113 #54 Not tainted   [  259.429718] -----------------------------------------------------   [  259.436516] qemu-system-x86/10143 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:   [  259.444670] ff3b2b1c60305170 (&amp;amp;xa-&amp;gt;xa_lock#25){+.+.}-{3:3}, at: __domain_flush_pages+0x17c/0x4b0   [  259.454485]                  and this task is already holding:   [  259.460991] ff3b2b1c98504cc0 (&amp;amp;domain-&amp;gt;lock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync+0x25/0x60   [  259.470408] which would create a new lock dependency:   [  259.476041]  (&amp;amp;domain-&amp;gt;lock){-.-.}-{3:3} -&amp;gt; (&amp;amp;xa-&amp;gt;xa_lock#25){+.+.}-{3:3}   [  259.483615]                  but this new dependency connects a HARDIRQ-irq-safe lock:   [  259.492447]  (&amp;amp;domain-&amp;gt;lock){-.-.}-{3:3}   [  259.492449]                  ... which became HARDIRQ-irq-safe at:   [  259.503705]   lock_acquire+0xb6/0x2e0   [  259.507790]   _raw_spin_lock_irqsave+0x3e/0x60   [  259.512748]   amd_iommu_flush_iotlb_all+0x20/0x50   [  259.517996]   iommu_dma_free_iova.isra.0+0x1b8/0x1e0   [  259.523534]   __iommu_dma_unmap+0xc2/0x140   [  259.528100]   iommu_dma_unmap_phys+0x55/0xc0   [  259.532863]   dma_unmap_phys+0x274/0x2e0   [  259.537238]   dma_unmap_page_…&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 114 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix IRQ unsafe locking in gdom allocation Lockdep complains:   [  259.410489] =====================================================   [  259.417287] WARNING: HARDIRQ-safe -&amp;gt; HARDIRQ-unsafe lock order detected   [  259.424667] 7.0.0-g51db1d8d2113 #54 Not tainted   [  259.429718] -----------------------------------------------------   [  259.436516] qemu-system-x86/10143 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:   [  259.444670] ff3b2b1c60305170 (&amp;amp;xa-&amp;gt;xa_lock#25){+.+.}-{3:3}, at: __domain_flush_pages+0x17c/0x4b0   [  259.454485]                  and this task is already holding:   [  259.460991] ff3b2b1c98504cc0 (&amp;amp;domain-&amp;gt;lock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync+0x25/0x60   [  259.470408] which would create a new lock dependency:   [  259.476041]  (&amp;amp;domain-&amp;gt;lock){-.-.}-{3:3} -&amp;gt; (&amp;amp;xa-&amp;gt;xa_lock#25){+.+.}-{3:3}   [  259.483615]                  but this new dependency connects a HARDIRQ-irq-safe lock:   [  259.492447]  (&amp;amp;domain-&amp;gt;lock){-.-.}-{3:3}   [  259.492449]                  ... which became HARDIRQ-irq-safe at:   [  259.503705]   lock_acquire+0xb6/0x2e0   [  259.507790]   _raw_spin_lock_irqsave+0x3e/0x60   [  259.512748]   amd_iommu_flush_iotlb_all+0x20/0x50   [  259.517996]   iommu_dma_free_iova.isra.0+0x1b8/0x1e0   [  259.523534]   __iommu_dma_unmap+0xc2/0x140   [  259.528100]   iommu_dma_unmap_phys+0x55/0xc0   [  259.532863]   dma_unmap_phys+0x274/0x2e0   [  259.537238]   dma_unmap_page_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68347</guid>
    </item>
  </channel>
</rss>
