From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E6E194FC8D6 for ; Wed, 16 Sep 2026 10:36:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789554991; cv=none; b=BvbJesaWm8VLXhCu0WPv6lFdqa8NqeBx5rIN6GlUIS0n/MCz758eF8DvKcDr9drbyw1WtJ3F4dfzEy/Vl9zAWqYuSwwkoXYz8OLD94BRXx03nSu/l/6mDiOeJ1wzJJS2p0IRhdiii7ZcDg7tltI//lGhkvMg9WBkYLmaZ7rDAyE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789554991; c=relaxed/simple; bh=Ai+zWE4BWc2PhUWhLtCO+Axnf43MFpYVMYH1EtmxrGE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=G858FKV0e9LYVzmiWZ+zY/E9lFtYbCCWjNCvC+3npRBVXx/QK65RzaKjnmUnvMmLV0JzwMHA5X74XEo4ip2UDxk1Es9Df1/GlT6sfcPUAuyk6xpC5Kp2ZjZA5vapCkN6Y9Hp/Jp02rRbTD4ymRrJmQwsgG7iB8eeNj4h3o/0en8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=bXOBp690; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="bXOBp690" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C7AF71F000FF; Wed, 16 Sep 2026 10:36:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789554974; bh=4E56P8Cf3xSxHq9cQ8NrGolr8+iWxdIH1LsxquEgnys=; h=From:To:Cc:Subject:Date:Reply-To; b=bXOBp690r23E534KH4pxN/66fejwCRUge8pV5vB3zSR58dnXA7s/z0gsypPOtIULI WL3TRTizIn4oDkIkp3AE5Z7qy0NRfWSEv8I20vRCrZg8A6ex26NRalaMwc/FBZ4dfp EE/xufsPlF7NcdTp2DDqK4gmpgFPDLhmQzkTa7PQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89865: scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers Date: Wed, 16 Sep 2026 11:29:55 +0100 Message-ID: <2026091623-CVE-2026-89865-e251@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4123; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=BaunOG7DjmCXJ7RnfM0FyK5c+UspNmtM5u8uSzhHFXg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8ptDeNNqFdv+FVq/Kn/PsnBJqaXXom1CC52k36Vuc 8r3mTerI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACbiJM4wVzjayumww//fHT02 S+9Waxp8CHLYx7BgcWqIfwF7U+ryOS3V/jeiLARXfkwEAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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