CVE-2026-43054

Medium

In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcm_loop: Drain commands in target_reset handler tcm_loop_target_reset() violates the SCSI EH contract: it returns SUCCESS without draining any in-flight commands. The SCSI EH documentation (scsi_eh.rst) requires that when a reset handler returns SUCCESS the driver has made lower layers "forget about timed out scmds" and is ready for new commands. Every other SCSI LLD (virtio_scsi, mpt3sas, ipr, scsi_debug, mpi3mr) enforces this by draining or completing outstanding commands before returning SUCCESS. Because tcm_loop_target_reset() doesn't drain, the SCSI EH reuses in-flight scsi_cmnd structures for recovery commands (e.g. TUR) while the target core still has async completion work queued for the old se_cmd. The memset in queuecommand zeroes se_lun and lun_ref_active, causing transport_lun_remove_cmd() to skip its percpu_ref_put(). The leaked LUN reference prevents transport_clear_lun_ref() from completing, hanging configfs LUN unlink forever in D-state: INFO: task rm:264 blocked for more than 122 seconds. rm D 0 264 258 0x00004000 Call Trace: __schedule+0x3d0/0x8e0 schedule+0x36/0xf0 transport_clear_lun_ref+0x78/0x90 [target_core_mod] core_tpg_remove_lun+0x28/0xb0 [target_core_mod] target_fabric_port_unlink+0x50/0x60 [target_core_mod] configfs_unlink+0x156/0x1f0 [configfs] vfs_unlink+0x109/0x290 do_unlinkat+0x1d5/0x2d0 Fix this by making tcm_loop_target_reset() actually drain commands: 1. Issue TMR_LUN_RESET via tcm_loop_issue_tmr() to drain all commands that the target core knows about (those not yet CMD_T_COMPLETE). 2. Use blk_mq_tagset_busy_iter() to iterate all started requests and flush_work() on each se_cmd — this drains any deferred completion work for commands that already had CMD_T_COMPLETE set before the TMR (which the TMR skips via __target_check_io_state()). This is the same pattern used by mpi3mr, scsi_debug, and libsas to drain outstanding commands during reset.

Package Linux Kernel
Published 2026-05-01
Last modified 2026-05-07
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

5.5

out of 10
Medium
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-772

CVE-2026-43054 is a Missing Release of Resource after Effective Lifetime vulnerability

What is Missing Release of Resource after Effective Lifetime?

The product does not release a resource after its effective lifetime has ended. Learn more on MITRE CWE

Affected versions

Linux kernel versions 5.13 and later are affected. Fixed in 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12, 7.0 and their respective stable series.

Affected from
≥ 5.13
Fixed in
✓ 5.15.203 5.15.x ✓ 6.1.168 6.1.x ✓ 6.6.134 6.6.x ✓ 6.12.81 6.12.x ✓ 6.18.22 6.18.x ✓ 6.19.12 6.19.x ✓ 7.0

References

The following references provide additional information about CVE-2026-43054 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2026-43054?

    CVE-2026-43054 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Missing Release of Resource after Effective Lifetime flaw (CWE-772) . It affects Linux kernel versions from 5.13 onward and has been patched in 5.15.203, 6.1.168, 6.6.134 and others. CVE-2026-43054 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2026-43054?

    CVE-2026-43054 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H .

  • Is there a patch available for CVE-2026-43054?

    Yes — CVE-2026-43054 has been patched. Fixed versions include 5.15.203, 6.1.168, 6.6.134 and others. If you are running Linux kernel 5.13 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-43054 actively exploited?

    No — CVE-2026-43054 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

  • What is Missing Release of Resource after Effective Lifetime (CWE-772)?

    The product does not release a resource after its effective lifetime has ended. View CWE-772 on MITRE CWE →