CVE-2026-72083
Description
A flaw was found in the Linux kernel's iSCSI target core. This use-after-free vulnerability occurs in the core_scsi3_emulate_pro_register_and_move() function. When processing iSCSI TransportIDs, a memory buffer is prematurely unmapped while still being referenced, particularly when the parameter list spans multiple pages. An attacker could potentially exploit this to cause a system crash, leading to a denial of service.
Statement
This vulnerability is rated as Important severity because an authenticated remote client can trigger a kernel-level use-after-free condition on an exposed storage target, potentially causing a system crash or privilege escalation. Under default Red Hat Enterprise Linux installations, the kernel LIO SCSI target framework is inactive unless administrators explicitly configure the system to serve block storage over iSCSI. Consequently, hosts acting exclusively as storage initiators or standard servers without active SCSI target configurations remain unexposed to this flaw.
Mitigation
To mitigate this flaw on hosts that do not operate as storage target servers, prevent the LIO target kernel modules from loading:
1. Create a configuration file to prevent loading the target modules:
# echo "install iscsi_target_mod /bin/true" > /etc/modprobe.d/disable-iscsi_target.conf
# echo "install target_core_mod /bin/true" > /etc/modprobe.d/disable-target_core.conf
2. Stop the SCSI target daemon if active:
# systemctl stop target.service
Warning: Modifying kernel module loading or stopping target.service requires a service restart or system reboot, and will immediately interrupt active storage connections on systems acting as storage targets.
If the machine must function as an iSCSI target, use network firewall rules to restrict access to the iSCSI target port (TCP port 3260) strictly to authorized initiator hosts.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.8 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.