<?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 02:56:33 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-40118</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-40118</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-40118</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1048 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-1048</link>
      <description>certfr-2025-avi-1048</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-1048</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40118</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40118</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 167 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod Since commit f7b705c238d1 (&amp;#34;scsi: pm80xx: Set phy_attached to zero when device is gone&amp;#34;) UBSAN reports:   UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17   index 28 is out of range for type &amp;#39;pm8001_phy [16]&amp;#39; on rmmod when using an expander. For a direct attached device, attached_phy contains the local phy id. For a device behind an expander, attached_phy contains the remote phy id, not the local phy id. I.e. while pm8001_ha will have pm8001_ha-&amp;gt;chip-&amp;gt;n_phy local phys, for a device behind an expander, attached_phy can be much larger than pm8001_ha-&amp;gt;chip-&amp;gt;n_phy (depending on the amount of phys of the expander). E.g. on my system pm8001_ha has 8 phys with phy ids 0-7.  One of the ports has an expander connected.  The expander has 31 phys with phy ids 0-30. The pm8001_ha-&amp;gt;phy array only contains the phys of the HBA.  It does not contain the phys of the expander.  Thus, it is wrong to use attached_phy to index the pm8001_ha-&amp;gt;phy array for a device behind an expander. Thus, we can only clear phy_attached for devices that are directly attached.&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 167 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod Since commit f7b705c238d1 (&amp;#34;scsi: pm80xx: Set phy_attached to zero when device is gone&amp;#34;) UBSAN reports:   UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17   index 28 is out of range for type &amp;#39;pm8001_phy [16]&amp;#39; on rmmod when using an expander. For a direct attached device, attached_phy contains the local phy id. For a device behind an expander, attached_phy contains the remote phy id, not the local phy id. I.e. while pm8001_ha will have pm8001_ha-&amp;gt;chip-&amp;gt;n_phy local phys, for a device behind an expander, attached_phy can be much larger than pm8001_ha-&amp;gt;chip-&amp;gt;n_phy (depending on the amount of phys of the expander). E.g. on my system pm8001_ha has 8 phys with phy ids 0-7.  One of the ports has an expander connected.  The expander has 31 phys with phy ids 0-30. The pm8001_ha-&amp;gt;phy array only contains the phys of the HBA.  It does not contain the phys of the expander.  Thus, it is wrong to use attached_phy to index the pm8001_ha-&amp;gt;phy array for a device behind an expander. Thus, we can only clear phy_attached for devices that are directly attached.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-40118</guid>
    </item>
  </channel>
</rss>
