CVE-2026-72083

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE

State
Published
Severity
9.8 Critical
Published
Aug 15, 2026
Updated
Oct 19, 2026
Reserved
Aug 9, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE

core_scsi3_emulate_pro_register_and_move() maps the PERSISTENT RESERVE OUT parameter list with transport_kmap_data_sg() and parses the destination TransportID with target_parse_pr_out_transport_id(). For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() returns the ISID in iport_ptr as a raw pointer into that mapped buffer.

The function then unmaps the buffer with transport_kunmap_data_sg() before dereferencing iport_ptr in strcmp(), __core_scsi3_locate_pr_reg() and core_scsi3_alloc_registration(). When the parameter list spans more than one page (PARAMETER LIST LENGTH > 4096), transport_kmap_data_sg() uses vmap() and transport_kunmap_data_sg() does vunmap(), so the kernel virtual address backing iport_ptr is torn down and every subsequent dereference is a use-after-free read of the unmapped region.

Keep the parameter list mapped until iport_ptr is no longer needed: drop the early transport_kunmap_data_sg() and unmap once on the success path, right before returning. The error paths already unmap through the existing "if (buf) transport_kunmap_data_sg(cmd)" at the out: label, which now runs on every post-map error exit because buf is no longer cleared early. Only reads of the mapping happen while spinlocks are held; the map and unmap calls remain outside any lock. The sibling caller core_scsi3_decode_spec_i_port() already uses the buffer before unmapping it and is left unchanged.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before 7d56f5c868d92c9d504a34a3ea450bce481c7f63Affected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before 59a2a5a37dc49a641ad6bc64aee34e5a61025ffdAffected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before 9f8076cc73dfa6b10155978c160587e986b22169Affected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before a040004846f1fbe687f6ec76d9ccc27b4ead42e4Affected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before 05b3e37433cf2eaf8867f1c16528aa347bb212abAffected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before cb7bdae7fba404852ade34b0c1445fbaf3e54fbbAffected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before ef2ee18fec92088c7d8877baf7674e89389ccd66Affected
  • 4949314c7283ea4f9ade182ca599583b89f7edd6 to before fda6a1f3c3d7047b5ce5654487649c2daa738bfcAffected
  • d2227f84ba0e97906153ac83db13213fb2e3938dAffected
  • 3.2.9 to before 3.3Affected
LinuxLinux
  • 3.3Affected
  • before 3.3Not affected
  • 5.10.261 through 5.10.*Not affected
  • 5.15.212 through 5.15.*Not affected
  • 6.1.178 through 6.1.*Not affected
  • 6.6.145 through 6.6.*Not affected
  • 6.12.97 through 6.12.*Not affected
  • 6.18.40 through 6.18.*Not affected
  • 7.1.5 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.