{"api_version":"1","generated_at":"2026-08-29T12:12:04+00:00","cve":"CVE-2026-80653","urls":{"html":"https://cve.report/CVE-2026-80653","api":"https://cve.report/api/cve/CVE-2026-80653.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80653","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80653"},"summary":{"title":"scsi: hisi_sas: Add slave_destroy interface for v3 hw","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Add slave_destroy interface for v3 hw\n\nWARNING is triggered when executing link reset of remote PHY and rmmod\nSAS driver simultaneously. Following is the WARNING log:\n\nWARNING: CPU: 61 PID: 21818 at drivers/base/core.c:1347 __device_links_no_driver+0xb4/0xc0\n Call trace:\n  __device_links_no_driver+0xb4/0xc0\n  device_links_driver_cleanup+0xb0/0xfc\n  __device_release_driver+0x198/0x23c\n  device_release_driver+0x38/0x50\n  bus_remove_device+0x130/0x140\n  device_del+0x184/0x434\n  __scsi_remove_device+0x118/0x150\n  scsi_remove_target+0x1bc/0x240\n  sas_rphy_remove+0x90/0x94\n  sas_rphy_delete+0x24/0x3c\n  sas_destruct_devices+0x64/0xa0 [libsas]\n  sas_revalidate_domain+0xe4/0x150 [libsas]\n  process_one_work+0x1e0/0x46c\n  worker_thread+0x15c/0x464\n  kthread+0x160/0x170\n  ret_from_fork+0x10/0x20\n ---[ end trace 71e059eb58f85d4a ]---\n\nDuring SAS phy up, link->status is set to DL_STATE_AVAILABLE in\ndevice_links_driver_bound, then this setting influences\n__device_links_no_driver() before driver rmmod and caused WARNING.\n\nAdd the slave_destroy interface to make sure link is removed after flush\nworkque.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-28 08:16:50","updated_at":"2026-08-29 07:16:48"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"8.4","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":8.4,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"8.4","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":8.4,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/cb414aff28e18e6f5cff9f87ea31376ed8af317b","name":"https://git.kernel.org/stable/c/cb414aff28e18e6f5cff9f87ea31376ed8af317b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/67b85a88265df19f049241d8c00571a5408f4eeb","name":"https://git.kernel.org/stable/c/67b85a88265df19f049241d8c00571a5408f4eeb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4867dba229292e13fc19ed865ec1839661952ff9","name":"https://git.kernel.org/stable/c/4867dba229292e13fc19ed865ec1839661952ff9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80653","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80653","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16fd4a7c5917097e9a3da03b39a92381eee40724 cb414aff28e18e6f5cff9f87ea31376ed8af317b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16fd4a7c5917097e9a3da03b39a92381eee40724 4867dba229292e13fc19ed865ec1839661952ff9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 16fd4a7c5917097e9a3da03b39a92381eee40724 67b85a88265df19f049241d8c00571a5408f4eeb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80653","cve":"CVE-2026-80653","epss":"0.001660000","percentile":"0.060700000","score_date":"2026-08-28","updated_at":"2026-08-29 00:12:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/scsi/hisi_sas/hisi_sas_v3_hw.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cb414aff28e18e6f5cff9f87ea31376ed8af317b","status":"affected","version":"16fd4a7c5917097e9a3da03b39a92381eee40724","versionType":"git"},{"lessThan":"4867dba229292e13fc19ed865ec1839661952ff9","status":"affected","version":"16fd4a7c5917097e9a3da03b39a92381eee40724","versionType":"git"},{"lessThan":"67b85a88265df19f049241d8c00571a5408f4eeb","status":"affected","version":"16fd4a7c5917097e9a3da03b39a92381eee40724","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/scsi/hisi_sas/hisi_sas_v3_hw.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.10"},{"lessThan":"5.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"5.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"5.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"5.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Add slave_destroy interface for v3 hw\n\nWARNING is triggered when executing link reset of remote PHY and rmmod\nSAS driver simultaneously. Following is the WARNING log:\n\nWARNING: CPU: 61 PID: 21818 at drivers/base/core.c:1347 __device_links_no_driver+0xb4/0xc0\n Call trace:\n  __device_links_no_driver+0xb4/0xc0\n  device_links_driver_cleanup+0xb0/0xfc\n  __device_release_driver+0x198/0x23c\n  device_release_driver+0x38/0x50\n  bus_remove_device+0x130/0x140\n  device_del+0x184/0x434\n  __scsi_remove_device+0x118/0x150\n  scsi_remove_target+0x1bc/0x240\n  sas_rphy_remove+0x90/0x94\n  sas_rphy_delete+0x24/0x3c\n  sas_destruct_devices+0x64/0xa0 [libsas]\n  sas_revalidate_domain+0xe4/0x150 [libsas]\n  process_one_work+0x1e0/0x46c\n  worker_thread+0x15c/0x464\n  kthread+0x160/0x170\n  ret_from_fork+0x10/0x20\n ---[ end trace 71e059eb58f85d4a ]---\n\nDuring SAS phy up, link->status is set to DL_STATE_AVAILABLE in\ndevice_links_driver_bound, then this setting influences\n__device_links_no_driver() before driver rmmod and caused WARNING.\n\nAdd the slave_destroy interface to make sure link is removed after flush\nworkque."}],"metrics":[{"cvssV3_1":{"baseScore":8.4,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The bug is reached when libsas tears down SCSI devices after a remote SAS PHY link reset (sas_revalidate_domain -> sas_destruct_devices) or when root unloads the hisi_sas v3 module; both require local kernel/driver activity, not remote network packets.\nAC:L - An attacker who controls a rogue SAS endpoint can repeatedly force link resets and race them against driver teardown; the failure is a deterministic missing sdev_destroy/device_link_remove on the hot path rather than a rare layout-dependent condition.\nPR:N - Triggering remote PHY link resets and SAS domain revalidation requires no Linux credentials—only a malicious or misbehaving device on the SAS fabric; root is only needed for the concurrent module-unload half of the reported race, not the dangling-link defect itself.\nUI:N - Exploitation does not require a victim to open files or mount filesystems; a rogue SAS device or automated PHY error/link-reset handling can drive the vulnerable teardown while the HBA is active.\nS:U - Impact is confined to the host kernel's SCSI/SAS driver and PM-runtime device-link state on the affected HiSilicon v3 HBA; it does not cross VM, container, or IOMMU security boundaries.\nC:H - Without sdev_destroy, managed device_links from scsi_device to hisi_hba survive consumer teardown, leaving consumer pointers to freed scsi_device memory that later hba PM-runtime or device-link walks can dereference (use-after-free read primitive).\nI:H - Stale managed device_links referencing freed scsi_devices corrupt kernel heap/link metadata and can be leveraged for further memory corruption during subsequent hba link management, matching kernel CNA guidance for lifecycle/UAF bugs.\nA:H - The reported race triggers WARN_ON in __device_links_no_driver (kernel oops under panic_on_warn) and dangling PM-runtime device_links from unfreed teardown can crash the host on later hba suspend/resume or module removal."}]}],"providerMetadata":{"dateUpdated":"2026-08-29T06:21:44.024Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cb414aff28e18e6f5cff9f87ea31376ed8af317b"},{"url":"https://git.kernel.org/stable/c/4867dba229292e13fc19ed865ec1839661952ff9"},{"url":"https://git.kernel.org/stable/c/67b85a88265df19f049241d8c00571a5408f4eeb"}],"title":"scsi: hisi_sas: Add slave_destroy interface for v3 hw","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80653","datePublished":"2026-08-28T06:49:00.717Z","dateReserved":"2026-08-26T14:34:25.779Z","dateUpdated":"2026-08-29T06:21:44.024Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 08:16:50","lastModifiedDate":"2026-08-29 07:16:48","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":8.4,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":2.5,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80653","Ordinal":"1","Title":"scsi: hisi_sas: Add slave_destroy interface for v3 hw","CVE":"CVE-2026-80653","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80653","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: hisi_sas: Add slave_destroy interface for v3 hw\n\nWARNING is triggered when executing link reset of remote PHY and rmmod\nSAS driver simultaneously. Following is the WARNING log:\n\nWARNING: CPU: 61 PID: 21818 at drivers/base/core.c:1347 __device_links_no_driver+0xb4/0xc0\n Call trace:\n  __device_links_no_driver+0xb4/0xc0\n  device_links_driver_cleanup+0xb0/0xfc\n  __device_release_driver+0x198/0x23c\n  device_release_driver+0x38/0x50\n  bus_remove_device+0x130/0x140\n  device_del+0x184/0x434\n  __scsi_remove_device+0x118/0x150\n  scsi_remove_target+0x1bc/0x240\n  sas_rphy_remove+0x90/0x94\n  sas_rphy_delete+0x24/0x3c\n  sas_destruct_devices+0x64/0xa0 [libsas]\n  sas_revalidate_domain+0xe4/0x150 [libsas]\n  process_one_work+0x1e0/0x46c\n  worker_thread+0x15c/0x464\n  kthread+0x160/0x170\n  ret_from_fork+0x10/0x20\n ---[ end trace 71e059eb58f85d4a ]---\n\nDuring SAS phy up, link->status is set to DL_STATE_AVAILABLE in\ndevice_links_driver_bound, then this setting influences\n__device_links_no_driver() before driver rmmod and caused WARNING.\n\nAdd the slave_destroy interface to make sure link is removed after flush\nworkque.","Type":"Description","Title":"scsi: hisi_sas: Add slave_destroy interface for v3 hw"}]}}}