<?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 07:46:09 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46141</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-46141</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://127.0.0.1:10001/vuln/bell-cve-2026-46141</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46141</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46141</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: fix kmemleak caused by incorrect chip_data lookup The kmemleak reports the following memory leak: Unreferenced object 0xc0000002a7fbc640 (size 64):   comm &amp;#34;kworker/8:1&amp;#34;, pid 540, jiffies 4294937872   hex dump (first 32 bytes):     01 00 00 00 00 00 00 00 00 00 09 04 00 04 00 00  ................     00 00 a7 81 00 00 0a c0 00 00 08 04 00 04 00 00  ................   backtrace (crc 177d48f6):     __kmalloc_cache_noprof+0x520/0x730     xive_irq_alloc_data.constprop.0+0x40/0xe0     xive_irq_domain_alloc+0xd0/0x1b0     irq_domain_alloc_irqs_parent+0x44/0x6c     pseries_irq_domain_alloc+0x1cc/0x354     irq_domain_alloc_irqs_parent+0x44/0x6c     msi_domain_alloc+0xb0/0x220     irq_domain_alloc_irqs_locked+0x138/0x4d0     __irq_domain_alloc_irqs+0x8c/0xfc     __msi_domain_alloc_irqs+0x214/0x4d8     msi_domain_alloc_irqs_all_locked+0x70/0xf8     pci_msi_setup_msi_irqs+0x60/0x78     __pci_enable_msix_range+0x54c/0x98c     pci_alloc_irq_vectors_affinity+0x16c/0x1d4     nvme_pci_enable+0xac/0x9c0 [nvme]     nvme_probe+0x340/0x764 [nvme] This occurs when allocating MSI-X vectors for an NVMe device. During allocation the XIVE code creates a struct xive_irq_data and stores it in irq_data-&amp;gt;chip_data. When the MSI-X irqdomain is later freed, xive_irq_free_data() is responsible for retrieving this structure and freeing it. However, after commit cc0cc23babc9 (&amp;#34;powerpc/xive: Untangle xive from child interrupt con…&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: fix kmemleak caused by incorrect chip_data lookup The kmemleak reports the following memory leak: Unreferenced object 0xc0000002a7fbc640 (size 64):   comm &amp;#34;kworker/8:1&amp;#34;, pid 540, jiffies 4294937872   hex dump (first 32 bytes):     01 00 00 00 00 00 00 00 00 00 09 04 00 04 00 00  ................     00 00 a7 81 00 00 0a c0 00 00 08 04 00 04 00 00  ................   backtrace (crc 177d48f6):     __kmalloc_cache_noprof+0x520/0x730     xive_irq_alloc_data.constprop.0+0x40/0xe0     xive_irq_domain_alloc+0xd0/0x1b0     irq_domain_alloc_irqs_parent+0x44/0x6c     pseries_irq_domain_alloc+0x1cc/0x354     irq_domain_alloc_irqs_parent+0x44/0x6c     msi_domain_alloc+0xb0/0x220     irq_domain_alloc_irqs_locked+0x138/0x4d0     __irq_domain_alloc_irqs+0x8c/0xfc     __msi_domain_alloc_irqs+0x214/0x4d8     msi_domain_alloc_irqs_all_locked+0x70/0xf8     pci_msi_setup_msi_irqs+0x60/0x78     __pci_enable_msix_range+0x54c/0x98c     pci_alloc_irq_vectors_affinity+0x16c/0x1d4     nvme_pci_enable+0xac/0x9c0 [nvme]     nvme_probe+0x340/0x764 [nvme] This occurs when allocating MSI-X vectors for an NVMe device. During allocation the XIVE code creates a struct xive_irq_data and stores it in irq_data-&amp;gt;chip_data. When the MSI-X irqdomain is later freed, xive_irq_free_data() is responsible for retrieving this structure and freeing it. However, after commit cc0cc23babc9 (&amp;#34;powerpc/xive: Untangle xive from child interrupt con…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46141</guid>
    </item>
  </channel>
</rss>
