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 1272B3D300D for ; Fri, 28 Aug 2026 06:51:36 +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=1787899897; cv=none; b=Qtm9G3P1BBFcd9k6qHBQ72a241Y7LRdmYgnFAWM+AFKr82jXrdYP6n/dSvc1mfPGo/llF4QVDcUHbWyrhN9k76qw86BOMrRAod0rZ9Oc72jft0PPHHmWeA/9KV05Y00aOLISow0926OXzlUe3iRY851wcbvdd2wdeQxOlVppnac= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787899897; c=relaxed/simple; bh=dsI/rHTIGl5ahEDpzqiB0guivZ20M0DAic15zNeMs4g=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=oGIPiNfO/Uu7ZOHGsYH89Vd6ggy9yS+Z5iy0NE5FSQXXtVLW8ryeIhibqSAMb2MNuyJkR3RecXjtFTJwszjj6OP5gd4vvjIesvkxGKU4PlaG2r6u7qleuGNjyONw9wIN39x2o7CYp4s+qzmB+WklnOvy+hsRmnSLun/dL5od054= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=VDVEYKuu; 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="VDVEYKuu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6C70A1F000E9; Fri, 28 Aug 2026 06:51:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787899896; bh=3+1SU/90XhiE0bzTsyNG4mXdnzHTI+EN1aVABJMCW1g=; h=From:To:Cc:Subject:Date:Reply-To; b=VDVEYKuuw3QutJhpS2jKEQNPVDDKMBNULxkMeUOODrACcadyYe9o/siz7ea9bq24f bwk5LmVC+cruipllGTMob9nEfq5/ghnzUA1cNtkH4GK4tZyvy7z2LiIllVA+gx44cC 7RMsKeYdD8iT21X2JW9FFuv2LZiwuj3dv6kfPRBk= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80653: scsi: hisi_sas: Add slave_destroy interface for v3 hw Date: Fri, 28 Aug 2026 08:49:30 +0200 Message-ID: <2026082844-CVE-2026-80653-105e@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=3094; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=sVqtNVo3ZG16MN0E1qrIKBdPgcWRNQ8kZgb33+pz10k=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkT9X1iPc7kW79+dsx98ewSMWt7rTNsu7lOrNrqLdv20 in7+mznjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIDgPDgnn+19fLJx9WmfxM xrE+4+UZ5oIibYYF5yrPeYl9qnNg3R9y4NcXx3OVT/9nAAA= 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: hisi_sas: Add slave_destroy interface for v3 hw WARNING is triggered when executing link reset of remote PHY and rmmod SAS driver simultaneously. Following is the WARNING log: WARNING: CPU: 61 PID: 21818 at drivers/base/core.c:1347 __device_links_no_driver+0xb4/0xc0 Call trace: __device_links_no_driver+0xb4/0xc0 device_links_driver_cleanup+0xb0/0xfc __device_release_driver+0x198/0x23c device_release_driver+0x38/0x50 bus_remove_device+0x130/0x140 device_del+0x184/0x434 __scsi_remove_device+0x118/0x150 scsi_remove_target+0x1bc/0x240 sas_rphy_remove+0x90/0x94 sas_rphy_delete+0x24/0x3c sas_destruct_devices+0x64/0xa0 [libsas] sas_revalidate_domain+0xe4/0x150 [libsas] process_one_work+0x1e0/0x46c worker_thread+0x15c/0x464 kthread+0x160/0x170 ret_from_fork+0x10/0x20 ---[ end trace 71e059eb58f85d4a ]--- During SAS phy up, link->status is set to DL_STATE_AVAILABLE in device_links_driver_bound, then this setting influences __device_links_no_driver() before driver rmmod and caused WARNING. Add the slave_destroy interface to make sure link is removed after flush workque. The Linux kernel CVE team has assigned CVE-2026-80653 to this issue. Affected and fixed versions =========================== Issue introduced in 5.10 with commit 16fd4a7c5917097e9a3da03b39a92381eee40724 and fixed in 6.18.40 with commit cb414aff28e18e6f5cff9f87ea31376ed8af317b Issue introduced in 5.10 with commit 16fd4a7c5917097e9a3da03b39a92381eee40724 and fixed in 7.1.5 with commit 4867dba229292e13fc19ed865ec1839661952ff9 Issue introduced in 5.10 with commit 16fd4a7c5917097e9a3da03b39a92381eee40724 and fixed in 7.2 with commit 67b85a88265df19f049241d8c00571a5408f4eeb 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-80653 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/hisi_sas/hisi_sas_v3_hw.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/cb414aff28e18e6f5cff9f87ea31376ed8af317b https://git.kernel.org/stable/c/4867dba229292e13fc19ed865ec1839661952ff9 https://git.kernel.org/stable/c/67b85a88265df19f049241d8c00571a5408f4eeb