CVE-2026-99682

Description

A flaw was found in the Linux kernel's virtio block driver (virtio_blk). This flaw allows a local user to cause a Denial of Service (DoS) by triggering a system crash. A race condition occurs during device freeze or suspend operations because the driver does not synchronously wait for pending request dispatchers to finish before releasing queue memory. When an interrupted dispatcher subsequently attempts to access the deallocated or reset device queue structures, the kernel crashes.

Statement

This vulnerability is rated as Moderate severity because exploiting it is restricted to a local denial of service and requires administrative privileges to initiate power management or device sleep states. The issue primarily impacts virtualized guest systems configured with virtio storage during power state transitions. Due to the precise timing required to trigger the race condition and the absence of any data corruption or confidentiality compromise, the overall risk to production environments is contained.

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)

Integrity,Other

Technical Impact: Alter Execution Logic; Unexpected State

The attacker can gain access to otherwise unauthorized resources.

Integrity,Other

Technical Impact: Modify Application Data; Modify Files or Directories; Modify Memory; Other

Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.

Integrity,Other

Technical Impact: Other

The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.

Non-Repudiation

Technical Impact: Hide Activities

If a file or other resource is written in this method, as opposed to in a valid way, logging of the activity may not occur.

Non-Repudiation,Other

Technical Impact: Other

In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.

Other

Technical Impact: Unexpected State

The product may perform invalid actions when the resource is in an unexpected state.

Frequently Asked Questions

Want to get errata notifications? Sign up here.