CVE-2026-99202

scsi: libsas: Fix SMP IO deadlock during HA resume

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: libsas: Fix SMP IO deadlock during HA resume smp_execute_task_sg() calls pm_runtime_get_sync() on the host before issuing an SMP command. When that command is itself issued from the HA resume path, the get_sync() deadlocks: it waits for the ongoing resume (the device is RPM_RESUMING), while the resume is blocked in sas_drain_work() waiting for that same SMP IO to complete. The deadlock needs an expander-attached SATA disk. During sas_resume_ha() -> sas_drain_work(), DISCE_RESUME -> sas_resume_sata() -> ata_sas_port_resume() requests ATA_EH_RESET, and the hard reset for such a disk is done via SMP PHY CONTROL (sas_ata_hard_reset() -> sas_phy_reset() -> sas_smp_phy_control() -> smp_execute_task_sg()). Direct-attached SATA resets through lldd_control_phy() and SSP devices use TMFs, so neither hits this. Replace the get_sync()/put_sync() pair with pm_runtime_get_noresume()/pm_runtime_put(). smp_execute_task_sg() only needs to hold off autosuspend while the SMP is in flight, and it must not try to resume the host: a sync resume issued from the HA resume path itself is what deadlocks, and by the time sas_resume_ha() runs, hw_init has already reinitialized the hardware, so the device is accessible without one. The usage reference is still required. Discovery work normally runs inside an event worker's PM reference, taken at sas_notify_port_event() notify time and held until the handler has flushed the disco queue. sas_rediscover_ex_phy() however requeues DISCE_REVALIDATE_DOMAIN from within the revalidation worker itself, and flush_workqueue() does not wait for work items queued during execution, so that chained revalidation runs with no outer PM reference - without the get_noresume(), its SMP could race autosuspend. For the BSG path, sas_smp_handler() is the only caller which may find the host autosuspended: expander SMP requests do not go through any SCSI device request queue, so nothing else in that path holds the host awake. Resume it there with pm_runtime_resume_and_get() and check the result.

Key facts

Published
28 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.174% likely to be exploited in the next 30 days, higher than 6.901% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 09357f067122e2e28ec52e27013a1660a1571618 up to but excluding ab91a558084fdb8cca4919ffb769ca4328e91bbd (affected)
  • e50a6523a603594a6d92cdecfe11997d639410a3 up to but excluding 6078a5369f9e8d22bb03b8890cb0bb47c91a5017 (affected)
  • c391b5899dd46485a5893696c12ae3e95a3a7325 up to but excluding 7004c18c38aaa2b87164b54dd77c320b4c63b89b (affected)
  • 9e24b47ef81d43b3fb1b14294f09991640c79fcc up to but excluding c9fb89246d9922ac0a45d504adb03e0bb971310c (affected)
  • 3dbbbf656b850c9c8de05df6ad4a1dfc6ff02845 up to but excluding 08b95ef36a64c3ae4490794bed3c35d0c3354e85 (affected)
  • 3dbbbf656b850c9c8de05df6ad4a1dfc6ff02845 up to but excluding 81e097a064b28b4a1f6ca1a8b433e659c1bd64c0 (affected)
  • b9c44a14062093e9fc2d6bddc696cfceadb482d7 (affected)
  • 6.1.183 up to but excluding 6.1.191 (affected)
  • 6.6.151 up to but excluding 6.6.161 (affected)
  • 6.12.103 up to but excluding 6.12.115 (affected)
  • 6.18.44 up to but excluding 6.18.59 (affected)
  • 7.1.8 up to but excluding 7.2 (affected)
LinuxLinux
  • Default status: affected
  • 7.2 (affected)
  • 0 up to but excluding 7.2 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References