All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89865: scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers
Date: Wed, 16 Sep 2026 11:29:55 +0100	[thread overview]
Message-ID: <2026091623-CVE-2026-89865-e251@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers

The FRU and I2C bsg handlers stage their transfer in a DMA_POOL_SIZE
(256-byte) bounce buffer obtained from dma_pool_alloc(), which does not
zero the allocation. They initialize only a few leading bytes before
handing the buffer to qla2x00_write_sfp().

qla2x00_write_sfp() can override the transfer length with a user-supplied
value:

	if (len == 1)
		opt |= BIT_0;
	if (opt & BIT_0)
		len = *sfp;

*sfp is the first byte of the (user-controlled) payload, so len can grow
up to 255. The device then DMA-reads len bytes from the 256-byte pool
buffer. Since only a small prefix was written
(e.g. MAX_FRU_SIZE == 36 bytes for a FRU version, one byte for a FRU
status register), the hardware reads past the initialized region and
writes up to ~219 bytes of stale DMA-pool heap memory to the device
flash.

Allocate the buffer with dma_pool_zalloc() in all five FRU/I2C handlers
so any bytes beyond the initialized data are zero rather than stale heap
contents.

The Linux kernel CVE team has assigned CVE-2026-89865 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 5.10.270 with commit a476377a66897549dd49bee319f4df66623417b7
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 5.15.221 with commit 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 6.1.188 with commit 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 6.6.157 with commit 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 6.12.110 with commit 581590f560b74399151b3cbc88574424c2f3d2dc
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 6.18.51 with commit b157256c28086c434afd70cc78bf9b4d8caf1276
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 7.2.5 with commit a5501c42256235523c4dddf799f032dfbf4f4c77
	Issue introduced in 3.2 with commit 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 and fixed in 7.3-rc1 with commit b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-89865
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/scsi/qla2xxx/qla_bsg.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/a476377a66897549dd49bee319f4df66623417b7
	https://git.kernel.org/stable/c/09703bc7c0be3a7a155b0ff5f21f6765ba3f519c
	https://git.kernel.org/stable/c/97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8
	https://git.kernel.org/stable/c/84bde5ce4038d9ad811e5c994305bbfcbd7a9f79
	https://git.kernel.org/stable/c/581590f560b74399151b3cbc88574424c2f3d2dc
	https://git.kernel.org/stable/c/b157256c28086c434afd70cc78bf9b4d8caf1276
	https://git.kernel.org/stable/c/a5501c42256235523c4dddf799f032dfbf4f4c77
	https://git.kernel.org/stable/c/b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc

                 reply	other threads:[~2026-09-16 10:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026091623-CVE-2026-89865-e251@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.