CVE-2026-93781

scsi: core: Do not block on tag allocation in scsi_eh_lock_door()

N/A
Published: September 24, 2026 at 04:02 PM UTC
Updated: October 3, 2026 at 11:17 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: core: Do not block on tag allocation in scsi_eh_lock_door() scsi_eh_lock_door() is called from scsi_restart_operations() while the host is still in the SHOST_RECOVERY state, i.e. before the host is switched back to SHOST_RUNNING and scsi_run_host_queues() restarts the queues. It allocates a request via scsi_alloc_request() with no flags, so blk_mq_get_tag() may block waiting for a free sched tag when all tags are already in use. Those tags can be held by commands that were just requeued by scsi_eh_flush_done_q() during error handling. Such commands cannot be dispatched until the host leaves SHOST_RECOVERY and scsi_run_host_queues() is called - which only happens *after* scsi_eh_lock_door() returns. This forms a circular dependency: - scsi_eh_lock_door(), running in the SCSI error handler thread, waits for a sched tag held by a requeued command; - the requeued command cannot complete and release its sched tag until the error handler thread leaves scsi_restart_operations() and restart the queues. For devices with a single driver tag (e.g. USB storage) it is a guaranteed deadlock and I/O that can never be submitted. This problem has also been reproduced in our environment. Locking the door is a best-effort operation, and scsi_eh_lock_door() already returns silently when the request allocation fails. Pass BLK_MQ_REQ_NOWAIT to scsi_alloc_request() so the allocation fails instead of blocking when no tag is available. This breaks the circular dependency and allows the error handler to finish restarting the queues, after which the pending commands are dispatched normally.

Affected

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

2.6.16 ≤ v < 6.1.1892.6.16 ≤ v < 6.12.1112.6.16 ≤ v < 6.18.532.6.16 ≤ v < 6.6.1582.6.16 ≤ v < 7.22.6.166e68af666f5336254b5715dca591026b7324499a
Vendor states this is fixed in 261c80a6b23e34ba98bcf3f75317e35ecf0a08f0 (fixed)
Vendor states this is fixed in 3bc7af4cefac1c583f0607f6183a67012436aad9 (fixed)
Vendor states this is fixed in 6b450c277c106c4e31411067f025d1aaa27c2a02 (fixed)
Vendor states this is fixed in 732cb6bb37fd26863d5786522fb1997e7f5865b4 (fixed)
Vendor states this is fixed in dc9e1b6b9080dd6374cc9a38e4b53abca63c3b1b (fixed)
Vendor states this is fixed in 2.6.16 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (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