CVE-2026-72086

scsi: xen: scsiback: Free the command tag on the TMR submit-failure path

N/A
Published: August 15, 2026 at 05:52 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: xen: scsiback: Free the command tag on the TMR submit-failure path scsiback_device_action() obtains a command tag in scsiback_get_pend_req() and submits a task-management request with target_submit_tmr(). When target_submit_tmr() fails it returns < 0 and scsiback jumps to the err: label, which sends a response but frees nothing, leaking the tag. Impact: a pvSCSI guest can leak the command tags of a LUN's session, stopping the LUN, by issuing VSCSIIF_ACT_SCSI_ABORT or RESET requests whenever target_submit_tmr() fails. transport_generic_free_cmd() cannot be used here. By the time target_submit_tmr() returns an error it has already run __target_init_cmd() (so se_cmd->cmd_kref is one, not zero), and on its target_get_sess_cmd() error path it has freed se_cmd->se_tmr_req via core_tmr_release_req() while leaving SCF_SCSI_TMR_CDB set and the pointer dangling. Letting the command release run target_free_cmd_mem() would then double-free se_tmr_req. Use the same helper, which returns just the tag, on this path too.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.6 ≤ v < 5.15.2124.6 ≤ v < 6.1.1784.6 ≤ v < 6.12.974.6 ≤ v < 6.18.404.6 ≤ v < 6.6.1454.6 ≤ v < 7.1.54.6 ≤ v < 7.22dbcdf33dbf61f44b29adb52338282c3d7840d0e4.6
Vendor states this is fixed in 1357fb32d42ad8da193e6da285f09e6452feabda (fixed)
Vendor states this is fixed in 18d4f86816592586b38513543b5e1f9553bc271f (fixed)
Vendor states this is fixed in 255fb7b0cdc947b1c01929c7f133281342a3a6b5 (fixed)
Vendor states this is fixed in 4567ce79fe2f84c3dcc3a91b22a377cf482d33ad (fixed)
Vendor states this is fixed in 66aefc277ebb796ec285d550305535dc3fc0179f (fixed)
Vendor states this is fixed in 6c01f0439098f00a64b246dc27479602201382f7 (fixed)
Vendor states this is fixed in fbc1bdede66d0f2cde83b75d6524ce1a815bb69f (fixed)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card