CVE-2026-64003

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d4dddfecdbb5467bef158d4e1486459808357fef
generic

scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c740e13e7fe32d8e4d9a1699f65b8daf6709895a
generic

scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7205b58702273baf21d6ba7992e6ba15852325f7
generic

scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/475f2b37a78f4c698967a7f14f325f04e24c9175
generic

scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15fb19af49f2073ed77fad16aaabc648b0ca6800

Vendor Advisories for CVE-2026-64003(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 29× in last 7d / 158× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 206 total refreshes for this CVE.

  1. 2026-08-30 02:53 UTCEG score recompute
  2. 2026-08-30 02:53 UTCVendor advisory
  3. 2026-08-30 02:53 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 01:43 UTCEG score recompute
  7. 2026-08-28 01:43 UTCVendor advisory
  8. 2026-08-28 01:43 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 11:52 UTCVendor advisory
  11. 2026-08-27 11:52 UTCGHSA enrichment
  12. 2026-08-26 22:24 UTCEG score recompute
  13. 2026-08-26 22:24 UTCVendor advisory
  14. 2026-08-26 22:23 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 08:58 UTCVendor advisory
  17. 2026-08-26 08:58 UTCGHSA enrichment
  18. 2026-08-25 20:18 UTCEG score recompute
  19. 2026-08-25 20:18 UTCVendor advisory
  20. 2026-08-25 20:17 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 07:37 UTCVendor advisory
  23. 2026-08-25 07:36 UTCGHSA enrichment
  24. 2026-08-24 19:06 UTCEG score recompute
  25. 2026-08-24 19:05 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 03:44 UTCVendor advisory
  2. 2026-08-24 03:43 UTCGHSA enrichment
  3. 2026-08-23 14:50 UTCVendor advisory
  4. 2026-08-23 14:50 UTCGHSA enrichment
  5. 2026-08-23 02:19 UTCEG score recompute
  6. 2026-08-23 02:19 UTCVendor advisory
  7. 2026-08-23 02:19 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 13:44 UTCVendor advisory
  10. 2026-08-22 13:44 UTCGHSA enrichment
  11. 2026-08-22 01:13 UTCEG score recompute
  12. 2026-08-22 01:13 UTCVendor advisory
  13. 2026-08-22 01:13 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 12:41 UTCVendor advisory
  16. 2026-08-21 12:41 UTCGHSA enrichment
  17. 2026-08-21 00:07 UTCEG score recompute
  18. 2026-08-21 00:07 UTCVendor advisory
  19. 2026-08-21 00:07 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 11:35 UTCVendor advisory
  22. 2026-08-20 11:35 UTCGHSA enrichment
  23. 2026-08-19 23:03 UTCEG score recompute
  24. 2026-08-19 23:03 UTCVendor advisory
  25. 2026-08-19 23:03 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 08:22 UTCVendor advisory
  28. 2026-08-19 08:22 UTCGHSA enrichment
  29. 2026-08-18 19:49 UTCEG score recompute
  30. 2026-08-18 19:49 UTCVendor advisory
  31. 2026-08-18 19:49 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 01:54 UTCEG score recompute
  34. 2026-08-18 01:54 UTCVendor advisory
  35. 2026-08-18 01:54 UTCGHSA enrichment
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-17 13:22 UTCVendor advisory
  38. 2026-08-17 13:22 UTCGHSA enrichment
  39. 2026-08-17 00:51 UTCEG score recompute
  40. 2026-08-17 00:51 UTCVendor advisory
  41. 2026-08-17 00:51 UTCGHSA enrichment
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-16 12:19 UTCEG score recompute
  44. 2026-08-16 12:19 UTCVendor advisory
  45. 2026-08-16 12:19 UTCGHSA enrichment
  46. 2026-08-15 23:49 UTCVendor advisory
  47. 2026-08-15 23:49 UTCGHSA enrichment
  48. 2026-08-15 11:18 UTCEG score recompute
  49. 2026-08-15 11:18 UTCVendor advisory
  50. 2026-08-15 11:18 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 22:46 UTCVendor advisory
  53. 2026-08-14 22:46 UTCGHSA enrichment
  54. 2026-08-14 10:15 UTCEG score recompute
  55. 2026-08-14 10:15 UTCVendor advisory
  56. 2026-08-14 10:15 UTCGHSA enrichment
  57. 2026-08-13 22:00 UTCEPSS rescore
  58. 2026-08-13 21:44 UTCVendor advisory
  59. 2026-08-13 21:44 UTCGHSA enrichment
  60. 2026-08-13 09:13 UTCVendor advisory
  61. 2026-08-13 09:13 UTCGHSA enrichment
  62. 2026-08-12 20:41 UTCEG score recompute
  63. 2026-08-12 20:41 UTCVendor advisory
  64. 2026-08-12 20:41 UTCGHSA enrichment
  65. 2026-08-12 13:51 UTCEPSS rescore
  66. 2026-08-12 08:10 UTCVendor advisory
  67. 2026-08-12 08:10 UTCGHSA enrichment
  68. 2026-08-11 19:39 UTCEG score recompute
  69. 2026-08-11 19:39 UTCVendor advisory
  70. 2026-08-11 19:39 UTCGHSA enrichment
  71. 2026-08-11 07:08 UTCEG score recompute
  72. 2026-08-11 07:08 UTCVendor advisory
  73. 2026-08-11 07:08 UTCGHSA enrichment
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 18:37 UTCVendor advisory

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64003?
CVE-2026-64003 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: core: Run queues for all non-SDEVDEL devices from scsirunhostqueues While a SCSI host is in a recovery state, scsimqrequeue_cmd() will not set the requeue list for a requeued command to be kicked in the future. The…
When was CVE-2026-64003 disclosed?
CVE-2026-64003 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64003 actively exploited?
CVE-2026-64003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.4% of all scored CVEs.
What is the CVSS score of CVE-2026-64003?
CVE-2026-64003 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64003?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64003, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64003

Explore →

Is Your Infrastructure Affected by CVE-2026-64003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs