CVE-2026-99202

Source
https://cve.org/CVERecord?id=CVE-2026-99202
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99202.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99202
Downstream
Published
2026-10-28T10:35:56Z
Modified
2026-11-17T07:03:38Z
Summary
scsi: libsas: Fix SMP IO deadlock during HA resume
Details

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.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99202.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
09357f067122e2e28ec52e27013a1660a1571618
Fixed
ab91a558084fdb8cca4919ffb769ca4328e91bbd
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
e50a6523a603594a6d92cdecfe11997d639410a3
Fixed
6078a5369f9e8d22bb03b8890cb0bb47c91a5017
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
c391b5899dd46485a5893696c12ae3e95a3a7325
Fixed
7004c18c38aaa2b87164b54dd77c320b4c63b89b
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
9e24b47ef81d43b3fb1b14294f09991640c79fcc
Fixed
c9fb89246d9922ac0a45d504adb03e0bb971310c
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3dbbbf656b850c9c8de05df6ad4a1dfc6ff02845
Fixed
08b95ef36a64c3ae4490794bed3c35d0c3354e85
Fixed
81e097a064b28b4a1f6ca1a8b433e659c1bd64c0
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
b9c44a14062093e9fc2d6bddc696cfceadb482d7

Affected versions

v6.*
v6.1.183
v6.1.184
v6.1.185
v6.1.186
v6.1.187
v6.1.188
v6.1.189
v6.1.190
v6.12.103
v6.12.104
v6.12.105
v6.12.106
v6.12.107
v6.12.108
v6.12.109
v6.12.110
v6.12.111
v6.12.112
v6.12.113
v6.12.114
v6.18.44
v6.18.45
v6.18.46
v6.18.47
v6.18.48
v6.18.49
v6.18.50
v6.18.51
v6.18.52
v6.18.53
v6.18.54
v6.18.55
v6.18.56
v6.18.57
v6.18.58
v6.6.151
v6.6.152
v6.6.153
v6.6.154
v6.6.155
v6.6.156
v6.6.157
v6.6.158
v6.6.159
v6.6.160
v7.*
v7.1.10
v7.1.11
v7.1.12
v7.1.13
v7.1.8
v7.1.9

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99202.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.1.183
Fixed
6.1.191
Type
ECOSYSTEM
Events
Introduced
6.6.151
Fixed
6.6.161
Type
ECOSYSTEM
Events
Introduced
6.12.103
Fixed
6.12.115
Type
ECOSYSTEM
Events
Introduced
6.18.44
Fixed
6.18.59
Type
ECOSYSTEM
Events
Introduced
7.1.8
Fixed
7.2
Type
ECOSYSTEM
Events
Introduced
7.2.0
Fixed
7.2.13

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99202.json"