CVE-2026-64250

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

LoongArch: Report dying CPU to RCU in stop_this_cpu()

This is a port of MIPS commit 9f3f3bdc6d9dac1 ("MIPS: smp: report dying CPU to RCU in stop_this_cpu()"). smp_send_stop() parks all secondary CPUs in stop_this_cpu(). And the function marks the CPU offline for the scheduler via set_cpu_online(false) but never informs RCU, so RCU keeps expecting a quiescent state from CPUs that are now spinning forever with interrupts disabled.

As long as nothing waits for an RCU grace period after smp_send_stop() this is harmless, which is why it went unnoticed. However, since commit 91840be8f710370 ("irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT"), irq_work_sync() calls synchronize_rcu() on architectures without an irq_work self-IPI, i.e. where arch_irq_work_has_interrupt() returns false. Any irq_work_sync() issued in the reboot/shutdown/halt path after smp_send_stop() then blocks on a grace period that can never complete, hanging the reboot:

WARNING: CPU: 0 PID: 15 at kernel/irq_work.c:144 irq_work_queue_on ... rcu: INFO: rcu_sched detected stalls on CPUs/tasks: rcu: Offline CPU 1 blocking current GP. rcu: Offline CPU 2 blocking current GP. rcu: Offline CPU 3 blocking current GP.

This issue needs some hacks to reproduce, and it was not noticed on LoongArch because arch_irq_work_has_interrupt() usually returns true.

Call rcutree_report_cpu_dead() once interrupts are disabled, mirroring the generic CPU-hotplug offline path, so RCU stops waiting on the parked CPUs and grace periods can still complete. LoongArch shuts down all CPUs here without going through the CPU-hotplug mechanism, so this report is not otherwise issued.

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 17, 2026

Advisory Details (6)

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

LoongArch: Report dying CPU to RCU in stop_this_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Report dying CPU to RCU in stop_this_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Report dying CPU to RCU in stop_this_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90e254f18b8c224460082329dd5c42fd30995c2f
generic

LoongArch: Report dying CPU to RCU in stop_this_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/262dadc619e69ebeb97affd334cd1078a9704e98
generic

LoongArch: Report dying CPU to RCU in stop_this_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fa22de588a65880d6fe54c38c87fffe7d519f60
generic

LoongArch: Report dying CPU to RCU in stop_this_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0833b2b84c2fc1387f8165f0cbf6a02d67f647a5

Vendor Advisories for CVE-2026-64250(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (154 versions)7.1.3-1—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-64250?
CVE-2026-64250 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Report dying CPU to RCU in stopthiscpu() This is a port of MIPS commit 9f3f3bdc6d9dac1 ("MIPS: smp: report dying CPU to RCU in stopthiscpu()"). smpsendstop() parks all secondary CPUs in stopthiscpu(). And the function…
When was CVE-2026-64250 disclosed?
CVE-2026-64250 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64250 actively exploited?
CVE-2026-64250 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64250?
CVE-2026-64250 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64250, 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-64250

Explore →

Is Your Infrastructure Affected by CVE-2026-64250?

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

Start Free Scan →Browse All CVEs