CVE-2026-93781

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

State
Published
Severity
Not scored
Published
Sep 24, 2026
Updated
Oct 3, 2026
Reserved
Sep 18, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 6e68af666f5336254b5715dca591026b7324499a to before 3bc7af4cefac1c583f0607f6183a67012436aad9Affected
  • 6e68af666f5336254b5715dca591026b7324499a to before 6b450c277c106c4e31411067f025d1aaa27c2a02Affected
  • 6e68af666f5336254b5715dca591026b7324499a to before 261c80a6b23e34ba98bcf3f75317e35ecf0a08f0Affected
  • 6e68af666f5336254b5715dca591026b7324499a to before dc9e1b6b9080dd6374cc9a38e4b53abca63c3b1bAffected
  • 6e68af666f5336254b5715dca591026b7324499a to before 732cb6bb37fd26863d5786522fb1997e7f5865b4Affected
LinuxLinux
  • 2.6.16Affected
  • before 2.6.16Not affected
  • 6.1.189 through 6.1.*Not affected
  • 6.6.158 through 6.6.*Not affected
  • 6.12.111 through 6.12.*Not affected
  • 6.18.53 through 6.18.*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.