CVE & CISA-KEV Catalog

CVE-2026-43054

MEDIUM
5.5
CVSS v3
NVD

Description

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.

How to fix

Remediation Available
linuxDebian
Fixed in:6.1.170-1CVE-2026-43054
Fixed in:6.12.85-1CVE-2026-43054
Fixed in:6.19.12-1CVE-2026-43054
linuxUbuntu
Fixed in:5.15.0-186.196USN-8575-1
Fixed in:6.8.0-136.136USN-8567-1
linux-awsUbuntu
Fixed in:5.15.0-1112.119USN-8575-2
Fixed in:6.8.0-1061.64USN-8595-2
linux-aws-5.15Ubuntu
Fixed in:5.15.0-1112.119~20.04.1USN-8575-2
linux-aws-6.8Ubuntu
Fixed in:6.8.0-1061.64~22.04.1USN-8595-3
linux-aws-fipsUbuntu
Fixed in:5.15.0-1112.119+fips1USN-8575-2
Fixed in:6.8.0-1061.64+fips1USN-8595-3
linux-azureUbuntu
Fixed in:5.15.0-1117.126USN-8575-3
Fixed in:6.8.0-1063.71USN-8606-1
linux-azure-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.1USN-8620-1
linux-azure-6.8Ubuntu
Fixed in:6.8.0-1063.71~22.04.1USN-8606-1
linux-azure-fdeUbuntu
Fixed in:5.15.0-1117.126USN-8610-1
Fixed in:6.8.0-1062.69USN-8607-1
linux-azure-fde-5.15Ubuntu
Fixed in:5.15.0-1117.126~20.04.2USN-8620-1
linux-azure-fde-6.8Ubuntu
Fixed in:6.8.0-1062.69~22.04.1USN-8609-1
linux-azure-fipsUbuntu
Fixed in:5.15.0-1117.126+fips1USN-8620-2
Fixed in:6.8.0-1063.71+fips2USN-8608-1
linux-fipsUbuntu
Fixed in:5.15.0-186.196+fips1USN-8575-2
Fixed in:6.8.0-136.136+fips2USN-8574-2
linux-gcpUbuntu
Fixed in:5.15.0-1112.122USN-8575-1
Fixed in:6.8.0-1064.72USN-8567-1
linux-gcp-5.15Ubuntu
Fixed in:5.15.0-1112.122~20.04.1USN-8668-1
linux-gcp-6.8Ubuntu
Fixed in:6.8.0-1064.72~22.04.1USN-8567-1
linux-gcp-fipsUbuntu
Fixed in:5.15.0-1112.122+fips1USN-8575-1
Fixed in:6.8.0-1064.72+fips1USN-8574-1
linux-gkeUbuntu
Fixed in:5.15.0-1108.114USN-8575-1
Fixed in:6.8.0-1059.67USN-8567-1
linux-gkeopUbuntu
Fixed in:5.15.0-1095.103USN-8575-1
Fixed in:6.8.0-1046.50USN-8567-1
linux-hwe-5.15Ubuntu
Fixed in:5.15.0-186.196~20.04.1USN-8575-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-136.136~22.04.1USN-8619-1
linux-ibmUbuntu
Fixed in:5.15.0-1106.110USN-8575-2
Fixed in:6.8.0-1061.62USN-8574-3
linux-ibm-5.15Ubuntu
Fixed in:5.15.0-1106.110~20.04.1USN-8597-1
linux-ibm-6.8Ubuntu
Fixed in:6.8.0-1061.62~22.04.1USN-8574-3
linux-image-5.15.0-1053-nvidia-tegra-igxUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1053-nvidia-tegra-igx-rtUbuntu
Fixed in:5.15.0-1053.53USN-8576-2
linux-image-5.15.0-1064-nvidia-tegraUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2
linux-image-5.15.0-1064-nvidia-tegra-rtUbuntu
Fixed in:5.15.0-1064.66~20.04.1USN-8576-1
Fixed in:5.15.0-1064.66USN-8576-2
linux-image-5.15.0-1075-xilinx-zynqmpUbuntu
Fixed in:5.15.0-1075.79USN-8575-1

This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

0.11%probability of exploitation in 30 days
2ndpercentile

Low risk: more likely to be exploited than 2% of all known CVEs.

References

Related Vulnerabilities

Other CWE-772 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2003-0132Medium5.087%-Fix
CVE-2017-14495High7.584%-Fix
CVE-2021-22883High7.574%-Fix
CVE-2024-2398High8.636%-Fix
CVE-2020-9375High7.527%--
CVE-1999-1127High7.518%--

Common questions

How do I fix CVE-2026-43054?

Published advisories record a fix for 247 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.

Is CVE-2026-43054 being actively exploited?

Not that we know of. CVE-2026-43054 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.11% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.

How severe is CVE-2026-43054?

CVE-2026-43054 has a CVSS v3 base score of 5.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-43054 affect?

Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-5.15 (Ubuntu), and 243 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-43054
CVE-2026-43054 severity badge

Markdown

[![CVE-2026-43054](https://tridentstack.com/cve/badge/CVE-2026-43054.svg)](https://tridentstack.com/cve/CVE-2026-43054)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-43054"><img src="https://tridentstack.com/cve/badge/CVE-2026-43054.svg" alt="CVE-2026-43054"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-07.