{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-80653",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-80653"
  ],
  "published": "2026-08-28T06:50:33Z",
  "summary": "scsi: hisi_sas: Add slave_destroy interface for v3 hw",
  "details": "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.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80653"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cb414aff28e18e6f5cff9f87ea31376ed8af317b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4867dba229292e13fc19ed865ec1839661952ff9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/67b85a88265df19f049241d8c00571a5408f4eeb"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-29T06:25:05Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.4,
      "cvss_v3_severity": "High",
      "scenario": "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\u2014only 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."
    }
  }
}