CVE-2026-64534

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
9.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: 9.8Exploit: 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:

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path

In nvmet_tcp_try_recv_ddgst(), when a data digest mismatch is detected, nvmet_req_uninit() is called unconditionally. However, if the command arrived via the nvmet_tcp_handle_req_failure() path, nvmet_req_init() had returned false and percpu_ref_tryget_live() was never executed. The unconditional percpu_ref_put() inside nvmet_req_uninit() then causes a refcount underflow, leading to a WARNING in percpu_ref_switch_to_atomic_rcu, a use-after-free diagnostic, and eventually a permanent workqueue deadlock.

Check cmd->flags & NVMET_TCP_F_INIT_FAILED before calling nvmet_req_uninit(), matching the existing pattern in nvmet_tcp_execute_request().

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

Published

July 27, 2026

Last Modified

August 5, 2026

Advisory Details (7)

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

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4606467a75cfc16721937272ed29462a750b60c8
generic

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ed3c9d955e8cd6361f130623baa664a75fb345f
generic

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22ec7a9fe9153d2737ee9b2fa6d2e43a1491decf

Vendor Advisories for CVE-2026-64534(1)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (154 versions)7.1.3-1—

All Vendor Advisories

(1)

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 68× in last 7d / 294× 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 316 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64534?
CVE-2026-64534 is a critical vulnerability published on July 27, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: check INITFAILED before nvmetreq_uninit in digest error path In nvmettcptryrecvddgst(), when a data digest mismatch is detected, nvmetrequninit() is called unconditionally. However, if the command arrived via the…
When was CVE-2026-64534 disclosed?
CVE-2026-64534 was first published in the National Vulnerability Database on July 27, 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-64534 actively exploited?
CVE-2026-64534 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 65.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64534?
CVE-2026-64534 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64534, 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-64534

Explore →

Is Your Infrastructure Affected by CVE-2026-64534?

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

Start Free Scan →Browse All CVEs