CVE-2026-72084

Description

A flaw was found in the Linux kernel's SCSI target subsystem. An attacker, by submitting a specially crafted iSCSI TransportID during a PERSISTENT RESERVE OUT operation, could cause an out-of-bounds read. This vulnerability, which occurs due to unbounded parsing of the TransportID, can lead to a system crash, resulting in a Denial of Service (DoS). This can be exploited by a remote attacker or a guest in a virtualized environment.

Statement

An out-of-bounds read in the SCSI target PR OUT TransportID parser can occur because the iSCSI TransportID parser processes attacker-controlled descriptor data without knowing the number of bytes actually received. For FORMAT CODE 01b, iscsi_parse_pr_out_transport_id() previously used an unbounded strstr() to locate the ",i,0x" separator between the iSCSI initiator name and ISID. A malformed TransportID containing neither the expected separator nor a NUL terminator can therefore cause the search to continue beyond the end of the PR OUT parameter buffer. Additional unbounded string handling on error and insufficient validation of the descriptor's self-reported length can extend the same out-of-bounds access condition.

When the PR OUT parameter list spans multiple pages, transport_kmap_data_sg() can map the buffer as a multi-page vmap. An unbounded scan beyond the supplied data may then reach the trailing vmalloc guard page, resulting in a kernel page fault and oops. The demonstrated impact is therefore a kernel crash and denial of service.

The affected parser is reachable through fabrics that can deliver a crafted PR OUT request to a device exported through an iSCSI target portal group (TPG). The same target-core path can also be exposed across virtualization boundaries, including guest-to-host configurations using vhost-scsi. Consequently, exploitation does not necessarily require local code execution or privileges on the affected host. For a network-exposed iSCSI target, a remote initiator capable of reaching the exported storage can potentially supply the malformed TransportID directly. In practice, exposure is commonly restricted to storage, virtualization, or otherwise trusted internal networks, which substantially limits the attack surface compared with a generally exposed network service.

The directly demonstrated security impact is availability loss (A:H) through a host kernel crash. No attacker-visible information disclosure, controlled out-of-bounds write, privilege escalation, or arbitrary code execution has been demonstrated. However, because the vulnerable code performs unbounded parsing of attacker-controlled data and subsequently operates on pointers derived from that parsing, additional memory-safety impact cannot be completely excluded and can be considered in a paranoid assessment or manual review.

Mitigation

To mitigate this issue, prevent module iscsi_target_mod from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.

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 Score7.1N/A9.8
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactLowN/AHigh
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.