Look up another CVE · open CVE-2026-64003 in the interactive tracker
CVE-2026-64003
scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem drivers/scsi. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-64003 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
While a SCSI host is in a recovery state, scsi_mq_requeue_cmd() will not set the requeue list for a requeued command to be kicked in the future. The expectation is a call to scsi_run_host_queues() will kick all SCSI devices once the recovery state is cleared. However, scsi_run_host_queues() uses shost_for_each_device() which uses scsi_device_get() and so will ignore devices in a partially removed state like SDEV_CANCEL. But these devices may also have requeued requests, leaving their requests stuck from not being kicked and causing the removal process of the device to hang. scsi_run_host_queues() needs to run against more devices than the macro shost_for_each_device() allows. Instead of using the too limiting scsi_device_get() state checks, only ignore devices in SDEV_DEL state or when unable to acquire a reference. Attempt to run the queues for all other devices when scsi_run_host_queues() is called.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/scsi/scsi_lib.c
- What this is
- SCSI SUBSYSTEMMAINTAINERS section matched on drivers/scsi/ · linux-scsi@vger.kernel.org · Maintained
- Kernel module
- scsi_mod
Check it on the machine
grep -w CONFIG_SCSI /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w scsi_modPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidb
- b
- built in on some flavours, a module on others
- Build switch
- CONFIG_SCSI
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-07-19 (3 months ago)source
- CVSS
- 7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.44%, higher than 36.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/scsi
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.5 | 6.6.143 | 15fb19af49f2 |
| 6.5 | 6.12.93 | d4dddfecdbb5 |
| 6.5 | 6.18.35 | 475f2b37a78f |
| 6.5 | 7.0.12 | c740e13e7fe3 |
| 6.5 | 7.1 | 7205b5870227 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- The bug is in the SCSI core midlayer reached after host error recovery; on enterprise servers using kernel iSCSI (iscsi_tcp/libiscsi), a remote storage target can inject SCSI failures and then drive session teardown that calls scsi_remove_target(), all over TCP without local access.
- AC:LAttack complexity, low
- A malicious or compromised iSCSI peer controls both sides of the race by timing command failures, non-responsive task-management replies, and connection resets so SCSI EH recovery overlaps with device removal in SDEV_CANCEL.
- PR:NPrivileges required, none
- Exploitation requires no privileges on the victim host; the attacker acts as the remote iSCSI endpoint on an already-established session and needs no CAP_SYS_ADMIN, sysfs writes, or ioctl access.
- UI:NUser interaction, none
- No end-user action is required during exploitation; recovery and removal are driven automatically by kernel SCSI/iSCSI error-handling once the session exists.
- S:UScope, unchanged
- Impact is a kernel hang during SCSI device teardown on the same host; it does not cross a VM, IOMMU, or sandbox security boundary.
- C:NConfidentiality impact, none
- This is a queue-dispatch logic bug that leaves requeued requests stuck; there is no memory corruption, out-of-bounds access, or information disclosure.
- I:NIntegrity impact, none
- The flaw prevents requeued I/O from being kicked and blocks removal completion; it does not modify data or provide a write or code-execution primitive.
- A:HAvailability impact, high
- Stuck requeued requests leave devices in SDEV_CANCEL with queues never kicked after recovery, causing the device removal path to hang indefinitely (deadlock), potentially blocking storage teardown, module unload, or shutdown.