<?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 01:49:13 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38624</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38624</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-2025-38624</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0787 — 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-0787</link>
      <description>certfr-2025-avi-0787</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0787</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38624</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38624</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 207 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Clean up allocated IRQs on unplug When the root of a nested PCIe bridge configuration is unplugged, the pnv_php driver leaked the allocated IRQ resources for the child bridges&amp;#39; hotplug event notifications, resulting in a panic. Fix this by walking all child buses and deallocating all its IRQ resources before calling pci_hp_remove_devices(). Also modify the lifetime of the workqueue at struct pnv_php_slot::wq so that it is only destroyed in pnv_php_free_slot(), instead of pnv_php_disable_irq(). This is required since pnv_php_disable_irq() will now be called by workers triggered by hot unplug interrupts, so the workqueue needs to stay allocated. The abridged kernel panic that occurs without this patch is as follows:   WARNING: CPU: 0 PID: 687 at kernel/irq/msi.c:292 msi_device_data_release+0x6c/0x9c   CPU: 0 UID: 0 PID: 687 Comm: bash Not tainted 6.14.0-rc5+ #2   Call Trace:    msi_device_data_release+0x34/0x9c (unreliable)    release_nodes+0x64/0x13c    devres_release_all+0xc0/0x140    device_del+0x2d4/0x46c    pci_destroy_dev+0x5c/0x194    pci_hp_remove_devices+0x90/0x128    pci_hp_remove_devices+0x44/0x128    pnv_php_disable_slot+0x54/0xd4    power_write_file+0xf8/0x18c    pci_slot_attr_store+0x40/0x5c    sysfs_kf_write+0x64/0x78    kernfs_fop_write_iter+0x1b0/0x290    vfs_write+0x3bc/0x50c    ksys_write+0x84/0x140    system_call_exception+0x124/0x230    system_call_vectored_common+0x15c/0x2ec…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 207 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Clean up allocated IRQs on unplug When the root of a nested PCIe bridge configuration is unplugged, the pnv_php driver leaked the allocated IRQ resources for the child bridges&amp;#39; hotplug event notifications, resulting in a panic. Fix this by walking all child buses and deallocating all its IRQ resources before calling pci_hp_remove_devices(). Also modify the lifetime of the workqueue at struct pnv_php_slot::wq so that it is only destroyed in pnv_php_free_slot(), instead of pnv_php_disable_irq(). This is required since pnv_php_disable_irq() will now be called by workers triggered by hot unplug interrupts, so the workqueue needs to stay allocated. The abridged kernel panic that occurs without this patch is as follows:   WARNING: CPU: 0 PID: 687 at kernel/irq/msi.c:292 msi_device_data_release+0x6c/0x9c   CPU: 0 UID: 0 PID: 687 Comm: bash Not tainted 6.14.0-rc5+ #2   Call Trace:    msi_device_data_release+0x34/0x9c (unreliable)    release_nodes+0x64/0x13c    devres_release_all+0xc0/0x140    device_del+0x2d4/0x46c    pci_destroy_dev+0x5c/0x194    pci_hp_remove_devices+0x90/0x128    pci_hp_remove_devices+0x44/0x128    pnv_php_disable_slot+0x54/0xd4    power_write_file+0xf8/0x18c    pci_slot_attr_store+0x40/0x5c    sysfs_kf_write+0x64/0x78    kernfs_fop_write_iter+0x1b0/0x290    vfs_write+0x3bc/0x50c    ksys_write+0x84/0x140    system_call_exception+0x124/0x230    system_call_vectored_common+0x15c/0x2ec…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38624</guid>
    </item>
  </channel>
</rss>
