<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 20:22:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89864</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-89864</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://vulnerability.circl.lu/vuln/bell-cve-2026-89864</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89864</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-89864</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Bound i2c-&amp;gt;length in I2C bsg handlers&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access carries a 16-bit length field alongside a fixed
64-byte buffer:&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access {
		uint16_t device, offset, option, length;
		uint8_t  buffer[0x40];
	} __packed;&lt;/p&gt;
&lt;p&gt;qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied
i2c-&amp;gt;length without any bounds check. i2c is overlaid on a 256-byte
on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to
65535 overruns both:&lt;/p&gt;
&lt;p&gt;- write: memcpy(sfp, i2c-&amp;gt;buffer, i2c-&amp;gt;length) over-reads the stack and
    over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs
    i2c-&amp;gt;length bytes out of the 256-byte buffer.
  - read: qla2x00_read_sfp() DMAs i2c-&amp;gt;length bytes into the 256-byte sfp,
    then memcpy(i2c-&amp;gt;buffer, sfp, i2c-&amp;gt;length) overflows the 64-byte
    buffer inside the on-stack array.&lt;/p&gt;
&lt;p&gt;A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the
kernel stack. Reject requests whose length exceeds the buffer before any
copy or DMA transfer in both handlers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Bound i2c-&amp;gt;length in I2C bsg handlers&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access carries a 16-bit length field alongside a fixed
64-byte buffer:&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access {
		uint16_t device, offset, option, length;
		uint8_t  buffer[0x40];
	} __packed;&lt;/p&gt;
&lt;p&gt;qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied
i2c-&amp;gt;length without any bounds check. i2c is overlaid on a 256-byte
on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to
65535 overruns both:&lt;/p&gt;
&lt;p&gt;- write: memcpy(sfp, i2c-&amp;gt;buffer, i2c-&amp;gt;length) over-reads the stack and
    over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs
    i2c-&amp;gt;length bytes out of the 256-byte buffer.
  - read: qla2x00_read_sfp() DMAs i2c-&amp;gt;length bytes into the 256-byte sfp,
    then memcpy(i2c-&amp;gt;buffer, sfp, i2c-&amp;gt;length) overflows the 64-byte
    buffer inside the on-stack array.&lt;/p&gt;
&lt;p&gt;A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the
kernel stack. Reject requests whose length exceeds the buffer before any
copy or DMA transfer in both handlers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-89864</guid>
    </item>
    <item>
      <title>GHSA-vhpc-fmr8-vgcc</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-vhpc-fmr8-vgcc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Bound i2c-&amp;gt;length in I2C bsg handlers&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access carries a 16-bit length field alongside a fixed
64-byte buffer:&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access {
		uint16_t device, offset, option, length;
		uint8_t  buffer[0x40];
	} __packed;&lt;/p&gt;
&lt;p&gt;qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied
i2c-&amp;gt;length without any bounds check. i2c is overlaid on a 256-byte
on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to
65535 overruns both:&lt;/p&gt;
&lt;p&gt;- write: memcpy(sfp, i2c-&amp;gt;buffer, i2c-&amp;gt;length) over-reads the stack and
    over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs
    i2c-&amp;gt;length bytes out of the 256-byte buffer.
  - read: qla2x00_read_sfp() DMAs i2c-&amp;gt;length bytes into the 256-byte sfp,
    then memcpy(i2c-&amp;gt;buffer, sfp, i2c-&amp;gt;length) overflows the 64-byte
    buffer inside the on-stack array.&lt;/p&gt;
&lt;p&gt;A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the
kernel stack. Reject requests whose length exceeds the buffer before any
copy or DMA transfer in both handlers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: qla2xxx: Bound i2c-&amp;gt;length in I2C bsg handlers&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access carries a 16-bit length field alongside a fixed
64-byte buffer:&lt;/p&gt;
&lt;p&gt;struct qla_i2c_access {
		uint16_t device, offset, option, length;
		uint8_t  buffer[0x40];
	} __packed;&lt;/p&gt;
&lt;p&gt;qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied
i2c-&amp;gt;length without any bounds check. i2c is overlaid on a 256-byte
on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to
65535 overruns both:&lt;/p&gt;
&lt;p&gt;- write: memcpy(sfp, i2c-&amp;gt;buffer, i2c-&amp;gt;length) over-reads the stack and
    over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs
    i2c-&amp;gt;length bytes out of the 256-byte buffer.
  - read: qla2x00_read_sfp() DMAs i2c-&amp;gt;length bytes into the 256-byte sfp,
    then memcpy(i2c-&amp;gt;buffer, sfp, i2c-&amp;gt;length) overflows the 64-byte
    buffer inside the on-stack array.&lt;/p&gt;
&lt;p&gt;A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the
kernel stack. Reject requests whose length exceeds the buffer before any
copy or DMA transfer in both handlers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-vhpc-fmr8-vgcc</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-89864 — scsi: qla2xxx: Bound i2c-&gt;length in I2C bsg handlers</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-89864</link>
      <description>msrc_CVE-2026-89864</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-89864</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89864</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89864</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound i2c-&amp;gt;length in I2C bsg handlers struct qla_i2c_access carries a 16-bit length field alongside a fixed 64-byte buffer: 	struct qla_i2c_access { 		uint16_t device, offset, option, length; 		uint8_t  buffer[0x40]; 	} __packed; qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied i2c-&amp;gt;length without any bounds check. i2c is overlaid on a 256-byte on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to 65535 overruns both:   - write: memcpy(sfp, i2c-&amp;gt;buffer, i2c-&amp;gt;length) over-reads the stack and     over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs     i2c-&amp;gt;length bytes out of the 256-byte buffer.   - read: qla2x00_read_sfp() DMAs i2c-&amp;gt;length bytes into the 256-byte sfp,     then memcpy(i2c-&amp;gt;buffer, sfp, i2c-&amp;gt;length) overflows the 64-byte     buffer inside the on-stack array. A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the kernel stack. Reject requests whose length exceeds the buffer before any copy or DMA transfer in both handlers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound i2c-&amp;gt;length in I2C bsg handlers struct qla_i2c_access carries a 16-bit length field alongside a fixed 64-byte buffer: 	struct qla_i2c_access { 		uint16_t device, offset, option, length; 		uint8_t  buffer[0x40]; 	} __packed; qla2x00_write_i2c() and qla2x00_read_i2c() use the user-supplied i2c-&amp;gt;length without any bounds check. i2c is overlaid on a 256-byte on-stack buffer and sfp is a 256-byte DMA-pool buffer, so a length up to 65535 overruns both:   - write: memcpy(sfp, i2c-&amp;gt;buffer, i2c-&amp;gt;length) over-reads the stack and     over-writes the sfp heap buffer, and qla2x00_write_sfp() then DMAs     i2c-&amp;gt;length bytes out of the 256-byte buffer.   - read: qla2x00_read_sfp() DMAs i2c-&amp;gt;length bytes into the 256-byte sfp,     then memcpy(i2c-&amp;gt;buffer, sfp, i2c-&amp;gt;length) overflows the 64-byte     buffer inside the on-stack array. A caller holding CAP_SYS_RAWIO can use this to corrupt the heap and the kernel stack. Reject requests whose length exceeds the buffer before any copy or DMA transfer in both handlers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89864</guid>
    </item>
  </channel>
</rss>
