CVE-2026-64211

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

srcu: Don't queue workqueue handlers to never-online CPUs

While an srcu_struct structure is in the midst of switching from CPU-0 to all-CPUs state, it can attempt to invoke callbacks for CPUs that have never been online. Worse yet, it can attempt in invoke callbacks for CPUs that never will be online, even including imaginary CPUs not in cpu_possible_mask. This can cause hangs on s390, which is not set up to deal with workqueue handlers being scheduled on such CPUs. This commit therefore causes Tree SRCU to refrain from queueing workqueue handlers on CPUs that have not yet (and might never) come online.

Because callbacks are not invoked on CPUs that have not been online, it is an error to invoke call_srcu(), synchronize_srcu(), or synchronize_srcu_expedited() on a CPU that is not yet fully online. However, it turns out to be less code to redirect the callbacks from too-early invocations of call_srcu() than to warn about such invocations. This commit therefore also redirects callbacks queued on not-yet-fully-online CPUs to the boot CPU.

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

Published

July 24, 2026

Last Modified

August 11, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

srcu: Don't queue workqueue handlers to never-online CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

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

srcu: Don't queue workqueue handlers to never-online CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/593889c401426004bd0ea0f6d4fcece728b03420

Vendor Advisories for CVE-2026-64211(1)

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

Patch Availability(3)

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

(1 across 1 ecosystem)
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

(3)

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 19× in last 7d / 81× 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.

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

Frequently asked(5)

What is CVE-2026-64211?
CVE-2026-64211 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: srcu: Don't queue workqueue handlers to never-online CPUs While an srcu_struct structure is in the midst of switching from CPU-0 to all-CPUs state, it can attempt to invoke callbacks for CPUs that have never been online. Worse yet,…
When was CVE-2026-64211 disclosed?
CVE-2026-64211 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64211 actively exploited?
CVE-2026-64211 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64211?
CVE-2026-64211 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64211, 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-64211

Explore →

Is Your Infrastructure Affected by CVE-2026-64211?

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