<?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 15:08:19 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80620</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80620</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, 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-2026-80620</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-80620</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80620</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 152 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Revert &amp;#34;PCI/MSI: Unmap MSI-X region on error&amp;#34; This reverts commit 1a8d4c6ecb4c81261bcdf13556abd4a958eca202. Commit 1a8d4c6ecb4c (&amp;#34;PCI/MSI: Unmap MSI-X region on error&amp;#34;) added an iounmap(dev-&amp;gt;msix_base) on the error path of msix_capability_init() to release the MSI-X region when msix_setup_interrupts() fails. When msix_setup_interrupts() fails, the call chain is:   msix_setup_interrupts()     -&amp;gt; __msix_setup_interrupts()          struct pci_dev *dev __free(free_msi_irqs) = __dev;          ...          return ret;  // __free cleanup fires on error The __free(free_msi_irqs) cleanup calls pci_free_msi_irqs(), which already handles the unmap:   void pci_free_msi_irqs(struct pci_dev *dev)   {       pci_msi_teardown_msi_irqs(dev);       if (dev-&amp;gt;msix_base) {           iounmap(dev-&amp;gt;msix_base);   // already unmapped here           dev-&amp;gt;msix_base = NULL;     // and set to NULL       }   } So dev-&amp;gt;msix_base is unmapped and set to NULL before msix_setup_interrupts() returns to msix_capability_init(). The &amp;#34;goto out_unmap&amp;#34; introduced by commit 1a8d4c6ecb4c (&amp;#34;PCI/MSI: Unmap MSI-X region on error&amp;#34;) then calls iounmap() a second time on a NULL pointer. This was reproduced on Intel Emerald Rapids (192 CPUs) while running tools/testing/selftests/kexec/test_kexec_jump.sh:   WARNING: CPU#44 at iounmap+0x2a/0xe0   RIP: 0010:iounmap+0x2a/0xe0   RDI: 0000000000000000   Call Trace:    msix_capability_init+0x317/0x3f0    __pci_enable…&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 152 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Revert &amp;#34;PCI/MSI: Unmap MSI-X region on error&amp;#34; This reverts commit 1a8d4c6ecb4c81261bcdf13556abd4a958eca202. Commit 1a8d4c6ecb4c (&amp;#34;PCI/MSI: Unmap MSI-X region on error&amp;#34;) added an iounmap(dev-&amp;gt;msix_base) on the error path of msix_capability_init() to release the MSI-X region when msix_setup_interrupts() fails. When msix_setup_interrupts() fails, the call chain is:   msix_setup_interrupts()     -&amp;gt; __msix_setup_interrupts()          struct pci_dev *dev __free(free_msi_irqs) = __dev;          ...          return ret;  // __free cleanup fires on error The __free(free_msi_irqs) cleanup calls pci_free_msi_irqs(), which already handles the unmap:   void pci_free_msi_irqs(struct pci_dev *dev)   {       pci_msi_teardown_msi_irqs(dev);       if (dev-&amp;gt;msix_base) {           iounmap(dev-&amp;gt;msix_base);   // already unmapped here           dev-&amp;gt;msix_base = NULL;     // and set to NULL       }   } So dev-&amp;gt;msix_base is unmapped and set to NULL before msix_setup_interrupts() returns to msix_capability_init(). The &amp;#34;goto out_unmap&amp;#34; introduced by commit 1a8d4c6ecb4c (&amp;#34;PCI/MSI: Unmap MSI-X region on error&amp;#34;) then calls iounmap() a second time on a NULL pointer. This was reproduced on Intel Emerald Rapids (192 CPUs) while running tools/testing/selftests/kexec/test_kexec_jump.sh:   WARNING: CPU#44 at iounmap+0x2a/0xe0   RIP: 0010:iounmap+0x2a/0xe0   RDI: 0000000000000000   Call Trace:    msix_capability_init+0x317/0x3f0    __pci_enable…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80620</guid>
    </item>
  </channel>
</rss>
