VulnerabilityPublished 19 Jul 2026

CVE-2026-64003: Linux kernel · scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues

Source GCVE Database

Authoritative record:CVE-2026-64003· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in d4dddfecdbb5467bef158d4e1486459808357fef : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in d4dddfecdbb5467bef158d4e1486459808357fef, c740e13e7fe32d8e4d9a1699f65b8daf6709895a, 7205b58702273baf21d6ba7992e6ba15852325f7 +2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-rqvx-8pr4-6wfh

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < d4dddfecdbb5467bef158d4e1486459808357fef	Fixed in d4dddfecdbb5467bef158d4e1486459808357fef
LinuxLinux	Affected ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < c740e13e7fe32d8e4d9a1699f65b8daf6709895a	Fixed in c740e13e7fe32d8e4d9a1699f65b8daf6709895a
LinuxLinux	Affected ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < 7205b58702273baf21d6ba7992e6ba15852325f7	Fixed in 7205b58702273baf21d6ba7992e6ba15852325f7
LinuxLinux	Affected ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < 475f2b37a78f4c698967a7f14f325f04e24c9175	Fixed in 475f2b37a78f4c698967a7f14f325f04e24c9175
LinuxLinux	Affected ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < 15fb19af49f2073ed77fad16aaabc648b0ca6800	Fixed in 15fb19af49f2073ed77fad16aaabc648b0ca6800
LinuxLinux	Affected =6.5	Fixed in–

AI-suggested

The vulnerability has been resolved in the Linux kernel. No specific patch links are provided in the data, and no cloud service is involved. Users should apply the official Linux kernel updates that include this fix when available.

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.

Impact

The impact is that queued SCSI requests on devices in partial removal states could remain stuck, causing the device removal process to hang. This could lead to system resource issues or degraded system stability related to SCSI device management. There is no indication of remote code execution or privilege escalation from the provided data.

Summary

The vulnerability in the Linux kernel's SCSI core relates to the function scsi_run_host_queues(), which previously used shost_for_each_device() that relies on scsi_device_get() to iterate devices. This approach ignored devices in partial removal states like SDEV_CANCEL, which could still have requeued requests. As a result, these requests would not be processed, causing them to remain stuck and potentially hanging the device removal process. The fix modifies scsi_run_host_queues() to run queues for all devices except those in the SDEV_DEL state or when a reference cannot be acquired, ensuring no queued requests remain unprocessed during recovery.

References

Community reviews

Loading reviews…