CVE-2026-64017

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

blk-mq: pop cached request if it is usable

When submitting a bio to blk-mq, if the task should sleep after peeking a cached request, but before it pops it, the plug flushes and calls blk_mq_free_plug_rqs, freeing the cached_rqs. This creates a use-after-free bug. Fix this by popping the cached request before any possible blocking calls if it is suitable for use.

Popping this request first holds a queue reference, so avoid any serialization races with queue freezes and can safely proceed with dispatching that request to the driver. This potentially increases a timing window from when a driver wants to freeze its queue to when requests stop being dispatched. That scenario is off the fast path though, and drivers need to appropriately handle requests during a freeze request anyway.

The downside is the popped element needs to be individually freed when we performed a bio plug merge. The cached request would have had to be freed later anyway, but this patch does it inline with building the plug list instead of after flushing it.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 19, 2026

Advisory Details (2)

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

blk-mq: pop cached request if it is usable - kernel/git/stable/linux.git - Linux kernel stable tree

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

blk-mq: pop cached request if it is usable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/388468f7e7d1eab092cf2a39fdfb502e52019ec6

Vendor Advisories for CVE-2026-64017(2)

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

Patch Availability(7)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)
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

(7)

Data Freshness Timeline

(refreshed 32× in last 7d / 171× 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 218 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64017?
CVE-2026-64017 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: blk-mq: pop cached request if it is usable When submitting a bio to blk-mq, if the task should sleep after peeking a cached request, but before it pops it, the plug flushes and calls blkmqfreeplugrqs, freeing the cached_rqs. This…
When was CVE-2026-64017 disclosed?
CVE-2026-64017 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64017 actively exploited?
CVE-2026-64017 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64017?
CVE-2026-64017 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64017?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64017, 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-64017

Explore →

Is Your Infrastructure Affected by CVE-2026-64017?

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