cve.bz

CVE-2026-72084 linux linux: Out-of-bounds Read

9.8 criticalEPSS 0.7%Fix available

Critical (9.8) in linux linux. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: scsi: target: Bound PR-OUT TransportID parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move() hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with a further unbounded "%s"). An initiator can submit a TransportID whose iSCSI name contains neither a ",i,0x" substring nor a NUL terminator, filling the parameter list to its end, so the scan runs off the end of the buffer. When the parameter list spans more than one page the buffer is a multi-page vmap (transport_kmap_data_sg()), so the over-read walks into the trailing vmalloc guard page and oopses (KASAN: vmalloc-out-of-bounds in strstr). It is reachable by any fabric that delivers a PR OUT to a device exported through an iSCSI TPG, including a guest via vhost-scsi. Pass the number of received bytes down to the parser and validate the iSCSI TransportID's own self-described length (ADDITIONAL LENGTH + 4) once, up front: reject it if it is below the spc4r17 minimum or larger than the received buffer, then bound the separator search, the ISID walk and the name copy by that length. This is the length check the callers already perform after the parse (core_scsi3_decode_spec_i_port() compares tid_len against tpdl, core_scsi3_emulate_register_and_move() validates it against data_length), moved ahead of the scan. Also drop the unbounded "%s" of the unterminated name. Add per-format explicit name-length checks before copying into i_str, rather than silently truncating with min_t: for FORMAT CODE 00b reject if the descriptor body (tid_len - 4 bytes) cannot fit in i_str[TRANSPORT_IQN_LEN]; for FORMAT CODE 01b reject if the name portion (from &buf[4] up to the separator) cannot fit. Both checks make the bounds intent explicit at each format branch. While here, also reject a FORMAT CODE 01b TransportID whose ",i,0x" separator sits at the very end of the descriptor: that leaves an empty ISID and points the returned port nexus pointer at buf + tid_len, one past the descriptor, which the registration code (__core_scsi3_locate_pr_reg(), __core_scsi3_alloc_registration()) then dereferences as the ISID string -- the same over-read of the parameter buffer for a malformed descriptor.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-125 Out-of-bounds Read
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.266
  • Linux Linux: fixed in 5.15.212
  • Linux Linux: fixed in 6.1.178
  • Linux Linux: fixed in 6.6.145
  • Linux Linux: fixed in 6.12.97
  • Linux Linux: fixed in 6.18.40
  • Linux Linux: fixed in 7.1.5
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-72084 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72084?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72084?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72084 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.38 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.266
Linux5.155.15.212
Linux6.16.1.178
Linux6.66.6.145
Linux6.126.12.97
Linux6.186.18.40
Linux7.17.1.5
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.180-1DEBIAN-CVE-2026-72084
Debian13linux6.12.100-1DEBIAN-CVE-2026-72084
Debian14linux7.1.5-1DEBIAN-CVE-2026-72084
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-72084
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-72084
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-72084
Ubuntu22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-72084 USN-8875-1
Ubuntu22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-72084 USN-8875-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-72084 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-72084 USN-8875-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-72084 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-72084 USN-8876-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-72084 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-72084 USN-8877-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-72084 USN-9024-1
80 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4, Linux Enterprise Micro 5.3 and 2 morekernel-default5.14.21-150400.24.240.2SUSE-SU-2026:4284-1
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6kernel-default6.4.0-150600.23.135.1SUSE-SU-2026:4369-1
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.81.1SUSE-SU-2026:4254-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.38.1SUSE-SU-2026:23897-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSSkernel-64kb, kernel-default5.14.21-150400.24.240.2SUSE-SU-2026:4284-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 morekernel-default-base5.14.21-150400.24.240.2.150400.24.120.2SUSE-SU-2026:4284-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Server 15 SP4-LTSS and 1 morekernel-docs, kernel-syms, kernel-source and 1 more5.14.21-150400.24.240.1SUSE-SU-2026:4284-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSSkernel-64kb, kernel-source, kernel-default and 1 more5.14.21-150500.55.192.2SUSE-SU-2026:4667-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morekernel-default-base5.14.21-150500.55.192.2.150500.6.89.2SUSE-SU-2026:4667-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Server 15 SP5-LTSS and 1 morekernel-docs, kernel-syms5.14.21-150500.55.192.1SUSE-SU-2026:4667-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.328.1SUSE-SU-2026:4282-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_871-8.5.1SUSE-SU-2026:4282-1
36 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.38.1.160000.2.22openSUSE-SU-2026:21910-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.38.1openSUSE-SU-2026:21910-1
Alpaquita23linux-lts6.1.182-r0BELL-CVE-2026-72084
Alpaquita25linux-lts6.12.103-r0BELL-CVE-2026-72084
Alpaquitastreamlinux-lts6.18.43-r0BELL-CVE-2026-72084

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's 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.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelAffected
Red Hat Enterprise Linux 7kernel-rtAffected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-72084.

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON