VulnerabilityPublished 28 Oct 2026

CVE-2026-99202: Linux kernel · scsi: libsas: Fix SMP IO deadlock during HA resume

Source GCVE Database

Authoritative record:CVE-2026-99202

Not known to be exploited · fixed in c9fb89246d9922ac0a45d504adb03e0bb971310c : update Linux kernel when convenient.

Data as of 28 Oct 2026, 13:30 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in c9fb89246d9922ac0a45d504adb03e0bb971310c, 81e097a064b28b4a1f6ca1a8b433e659c1bd64c0, 08b95ef36a64c3ae4490794bed3c35d0c3354e85 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-pc8p-2j27-g7rj

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.18.44 <6.18.59 >=6.1.183 <6.2 >=6.6.151 <6.7 >=6.12.103 <6.13 >=7.1.8 <7.2	Fixed in c9fb89246d9922ac0a45d504adb03e0bb971310c 81e097a064b28b4a1f6ca1a8b433e659c1bd64c0 08b95ef36a64c3ae4490794bed3c35d0c3354e85 7.2 6.18.59 6.13 6.7 6.2
LinuxLinux	Affected =7.2	Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel that replaces the problematic pm_runtime_get_sync() call with pm_runtime_get_noresume(), preventing the deadlock during HA resume. Users should update to a Linux kernel version that includes this fix. No additional mitigations are required as the patch addresses the root cause.

Description

A deadlock vulnerability in the Linux kernel's SCSI libsas driver during high availability (HA) resume has been fixed. The issue occurs when smp_execute_task_sg() calls pm_runtime_get_sync() on the host during the HA resume path, causing a deadlock due to waiting on an ongoing resume while the resume waits for SMP IO completion. This deadlock specifically affects expander-attached SATA disks during the resume process.

Impact

This vulnerability can cause a deadlock in the Linux kernel's SCSI subsystem during HA resume operations involving expander-attached SATA disks. The deadlock halts the resume process, potentially leading to system hangs or unavailability of affected storage devices during resume. It does not affect directly attached SATA or SSP devices. There is no indication of exploitation in the wild or broader impact beyond the deadlock condition.

References

Community reviews

Loading reviews…