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_driv
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-80653 is a race condition vulnerability in the Linux kernel's HiSilicon SAS (Serial Attached SCSI) driver affecting v3 hardware. The vulnerability occurs when a remote PHY link reset is executed simultaneously with SAS driver module removal (rmmod), causing improper device link state management. This triggers a WARNING condition in the kernel's device core infrastructure when attempting to clean up device links without an active driver. The vulnerability affects Linux systems running affected kernel versions with HiSilicon SAS SCSI controllers, particularly in data center and enterprise environments where remote PHY resets and driver updates may occur concurrently.
While this CVE does not currently map to specific MITRE ATT&CK techniques, Casky's extended reasoning capabilities would detect the underlying patterns through kernel state machine analysis and driver lifecycle monitoring. Practitioners using Casky would observe anomalous behavior in system logs showing device_release_driver() execution during active device operations, coupled with __device_links_no_driver warnings that indicate improper resource cleanup sequences. The detection would focus on temporal correlation between two concurrent events—PHY reset operations and driver module operations—that create unsafe state transitions. Advanced practitioners would map this to T1529 (Service Stop) and persistence-related techniques where driver state corruption could be exploited, enabling Casky to flag the vulnerability through behavioral analysis of kernel subsystem interactions rather than signature-based detection.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-80653. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation