Skip to main content
VulnerabilityPublished Updated

CVE-2026-64003: Linux kernel · Uncontrolled Resource Consumption

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 17:16 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.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < d4dddfecdbb5467bef158d4e1486459808357fef
Fixed in
  • d4dddfecdbb5467bef158d4e1486459808357fef
LinuxLinuxAffected
  • ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < c740e13e7fe32d8e4d9a1699f65b8daf6709895a
Fixed in
  • c740e13e7fe32d8e4d9a1699f65b8daf6709895a
LinuxLinuxAffected
  • ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < 7205b58702273baf21d6ba7992e6ba15852325f7
Fixed in
  • 7205b58702273baf21d6ba7992e6ba15852325f7
LinuxLinuxAffected
  • ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < 475f2b37a78f4c698967a7f14f325f04e24c9175
Fixed in
  • 475f2b37a78f4c698967a7f14f325f04e24c9175
LinuxLinuxAffected
  • ≥ 8b566edbdbfb5cde31a322c57932694ff48125ed, < 15fb19af49f2073ed77fad16aaabc648b0ca6800
Fixed in
  • 15fb19af49f2073ed77fad16aaabc648b0ca6800
LinuxLinuxAffected
  • =6.5
Fixed in–

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.

References

Community reviews

Loading reviews…