VulnerabilityPublished 28 Oct 2026Updated 29 Oct 2026

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

Affects Linux kernelSource GCVE Database

Compare

Authoritative record:CVE-2026-99202· Medium

Not known to be exploited.

Data as of 29 Oct 2026, 22:38 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-10.10 7 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that replaces the synchronous runtime PM calls with non-resuming variants to prevent the deadlock. Users should update to patched Linux kernel versions that include this fix. No additional mitigation is required beyond applying the official patch.

Description

CVE-2026-99202 is a vulnerability in the Linux kernel's libsas SCSI subsystem that causes a deadlock during high availability (HA) resume operations involving SMP IO commands. The deadlock occurs when a synchronous runtime power management resume is triggered from the HA resume path, causing a circular wait between the resume process and SMP IO completion. This issue specifically affects expander-attached SATA disks and is resolved by changing the runtime PM calls to avoid synchronous resume during SMP IO. The vulnerability impacts certain Linux kernel versions used in Ubuntu distributions.

Impact

The vulnerability causes a deadlock in the Linux kernel's SCSI libsas driver during HA resume operations involving expander-attached SATA disks. This deadlock can halt the resume process, potentially impacting system availability and stability during power management events. It does not indicate remote code execution or data corruption but can cause system hangs related to storage device management.

Summary

The vulnerability in the Linux kernel's libsas SCSI driver involves a deadlock triggered during HA resume when smp_execute_task_sg() calls pm_runtime_get_sync() on the host before issuing an SMP command. If this command is issued from the HA resume path, the synchronous runtime PM resume deadlocks because it waits for the ongoing resume to complete while the resume is blocked waiting for the SMP IO to finish. This deadlock requires an expander-attached SATA disk and occurs during sas_resume_ha() operations involving hard resets via SMP PHY CONTROL. The fix replaces pm_runtime_get_sync()/put_sync() with pm_runtime_get_noresume()/put() to hold off autosuspend without triggering a resume, preventing the deadlock. Additional handling ensures proper runtime PM references during discovery and SMP request paths.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 22:38 UTC

Technical details

References

Community reviews

Related threats