CVE-2026-64281

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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

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:

svcrdma: wake sq waiters when the transport closes

Threads parked in svc_rdma_sq_wait() on sc_sq_ticket_wait or sc_send_wait can hang indefinitely in TASK_UNINTERRUPTIBLE state across transport teardown, pinning svc_xprt references and blocking svc_rdma_free().

The close path sets XPT_CLOSE before invoking xpo_detach and both wait_event predicates include an XPT_CLOSE term, but the predicates are re-evaluated only on wakeup. sc_sq_ticket_wait has no completion-driven wake path; it is advanced solely by the chained ticket handoff inside svc_rdma_sq_wait() itself. Without an explicit wake at close, parked threads never observe XPT_CLOSE, hold their svc_xprt_get reference forever, and svc_rdma_free() blocks on xpt_ref dropping to zero.

Two close entry points reach this transport. Local teardown runs svc_rdma_detach() from svc_handle_xprt() -> svc_delete_xprt() -> xpo_detach() on a worker thread. A remote disconnect arrives at svc_rdma_cma_handler(), which calls svc_xprt_deferred_close(): that sets XPT_CLOSE and enqueues the transport but does not access either RDMA waitqueue, so a worker already parked in svc_rdma_sq_wait() never re-evaluates its predicate. With every worker parked on this transport, no thread is available to run the local teardown either, and the wake site there is unreachable.

Introduce svc_rdma_xprt_deferred_close(), a thin svcrdma wrapper that calls svc_xprt_deferred_close() and then wakes both sc_sq_ticket_wait and sc_send_wait. Convert the svcrdma producers that called svc_xprt_deferred_close() directly: svc_rdma_cma_handler(), qp_event_handler(), svc_rdma_post_send_err(), svc_rdma_wc_send(), the sendto drop path, the rw completion error paths, and the recvfrom flush and read-list error paths.

Wake both waitqueues from svc_rdma_detach() as well. The synchronous svc_xprt_close() path (backchannel ENOTCONN, device removal via svc_rdma_xprt_done) reaches detach without flowing through svc_xprt_deferred_close() and therefore does not invoke the new helper.

[ cel: add svc_rdma_xprt_deferred_close() to complete the fix ]

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
39%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

svcrdma: wake sq waiters when the transport closes - kernel/git/stable/linux.git - Linux kernel stable tree

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

svcrdma: wake sq waiters when the transport closes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40eedc4253dbda0b29b7961200534dfcecb48ace

Vendor Advisories for CVE-2026-64281(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 21× in last 7d / 117× 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 147 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64281?
CVE-2026-64281 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: svcrdma: wake sq waiters when the transport closes Threads parked in svcrdmasqwait() on scsqticketwait or scsendwait can hang indefinitely in TASK_UNINTERRUPTIBLE state across transport teardown, pinning svc_xprt references and…
When was CVE-2026-64281 disclosed?
CVE-2026-64281 was first published in the National Vulnerability Database on July 25, 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-64281 actively exploited?
CVE-2026-64281 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 61.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64281?
CVE-2026-64281 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64281?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64281, 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-64281

Explore →

Is Your Infrastructure Affected by CVE-2026-64281?

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