CVE-2026-80653: scsi: hisi_sas: Add slave_destroy interface for v3 hw
In the Linux kernel, the following vulnerability has been resolved:
scsi: hisisas: Add slavedestroy 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 devicelinksnodriver+0xb4/0xc0 Call trace: devicelinksnodriver+0xb4/0xc0 devicelinksdrivercleanup+0xb0/0xfc devicereleasedriver+0x198/0x23c devicereleasedriver+0x38/0x50 busremovedevice+0x130/0x140 devicedel+0x184/0x434 scsiremovedevice+0x118/0x150 scsiremovetarget+0x1bc/0x240 sasrphyremove+0x90/0x94 sasrphydelete+0x24/0x3c sasdestructdevices+0x64/0xa0 [libsas] sasrevalidatedomain+0xe4/0x150 [libsas] processonework+0x1e0/0x46c workerthread+0x15c/0x464 kthread+0x160/0x170 retfromfork+0x10/0x20 ---[ end trace 71e059eb58f85d4a ]---
During SAS phy up, link->status is set to DLSTATEAVAILABLE in devicelinksdriverbound, then this setting influences devicelinksnodriver() before driver rmmod and caused WARNING.
Add the slavedestroy interface to make sure link is removed after flush workque.
Affected Software
Event History
Frequently Asked Questions
What systems are exposed to this issue?
Systems running the Linux kernel with the hisi_sas version 3 hardware driver are implicated. The warning occurs in a SAS configuration involving a remote PHY.
What event is needed to trigger the warning?
The warning is triggered when a remote PHY link reset and removal of the SAS driver module occur simultaneously. This is a timing-dependent driver teardown scenario rather than a condition described as reachable through normal standalone operation.
What does the fix change?
The fix adds a slave_destroy interface for version 3 hardware so that the device link is removed after the relevant workqueue is flushed. This prevents the link state from affecting driver cleanup during module removal.