CVE-2026-80720

Description

A flaw was found in the iomap component of the Linux kernel. The iomap_split_ioend function can cause a deadlock when it attempts to split bios that originate from iomap_ioend_bioset and the bioset is exhausted. This can lead to a system hang, resulting in a Denial of Service (DoS) for affected systems.

Statement

A denial of service flaw of moderate impact was found in the iomap subsystem of the Linux kernel as shipped in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2. The iomap_split_ioend() function can split bios that were originally allocated from the iomap_ioend_bioset mempool; when that mempool is exhausted, the split operation blocks waiting for memory that cannot be freed until in-flight I/O completes, resulting in a deadlock that hangs filesystem I/O. A local user able to perform file I/O on an affected mounted filesystem can trigger this condition, with reliable triggering depending on storage and filesystem configuration, causing a system hang or filesystem I/O stall (denial of service). No confidentiality or integrity impact is supported by the evidence. Red Hat Enterprise Linux 6, 7, 8, and 9 streams and Red Hat Enterprise Linux 10.0 are not affected because the iomap bio-splitting code that introduced this flaw is not present in those kernels. For the affected Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2 streams the fix is currently deferred to a future update; until then the residual risk is a local denial of service through an I/O deadlock when the bioset mempool becomes exhausted. The upstream CVE record assigns a CVSS score of 7.5 with a network attack vector, while Red Hat rates this flaw moderate with a CVSS score of 5.5 and a local attack vector because the issue is not network-reachable and requires local access to perform file I/O on an affected system.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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 Score5.5N/A7.5
Attack VectorLocalN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/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.