CVE-2026-99202

Description

A flaw was found in the Linux kernel's libsas subsystem, leading to a denial of service (DoS). When resuming a host adapter connected to an expander-attached storage drive, an internal deadlock condition can occur while executing management commands. A local user can trigger this vulnerability during device power management resume operations to cause an unrecoverable system hang.

Statement

This vulnerability is rated as Moderate severity because exploitation requires elevated administrative privileges to execute power state changes and is constrained to specialized hardware configurations. In typical enterprise environments, the issue only manifests on hosts equipped with Serial Attached SCSI (SAS) controllers connected to SATA drives through SAS expanders. While a deadlock during host adapter power recovery results in a localized system freeze, it cannot be exploited remotely and does not lead to data loss or confidentiality exposure.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.