CVE-2026-64534nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path
- 9.8CriticalCVSS base score
- 0.32%Exploitation in 30 daysEPSS · top 74% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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().
Timeline
ID reserved
By Linux
- 8 days later
· 8 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Awaiting Analysis | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.32% · top 74% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 91edfca6f8b364d60cde3ddefaf7d03ddf35774b – < 22ec7a9fe9153d2737ee9b2fa6d2e43a1491decf
- affected fda871c0ba5d2eed2cd1c881573168129da70058 – < ba35b1c674ca3841c0dfadd698f2c1b3ec542d4e
- affected fda871c0ba5d2eed2cd1c881573168129da70058 – < c7874dad84b20433c0fe3919f291a762d40de08b
- affected fda871c0ba5d2eed2cd1c881573168129da70058 – < e602c93b25bda4a9d0ff1791a4bdbfdcbb074af1
- affected fda871c0ba5d2eed2cd1c881573168129da70058 – < d306da8833e75f669d93424fd84940236f3850bc
- affected fda871c0ba5d2eed2cd1c881573168129da70058 – < 2ed3c9d955e8cd6361f130623baa664a75fb345f
- affected fda871c0ba5d2eed2cd1c881573168129da70058 – < 4606467a75cfc16721937272ed29462a750b60c8
- affected 4b17476d809273617d3317fa0d4ae78aa488d760
- affected 5.10.20 – < 5.10.261
- affected 5.11.3 – < 5.12
- affected 5.12
- unaffected < 5.12
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/22ec7a9fe9153d2737ee9b2fa6d2e43a1491decf (opens in a new tab)
- https://git.kernel.org/stable/c/ba35b1c674ca3841c0dfadd698f2c1b3ec542d4e (opens in a new tab)
- https://git.kernel.org/stable/c/c7874dad84b20433c0fe3919f291a762d40de08b (opens in a new tab)
- https://git.kernel.org/stable/c/e602c93b25bda4a9d0ff1791a4bdbfdcbb074af1 (opens in a new tab)
- https://git.kernel.org/stable/c/d306da8833e75f669d93424fd84940236f3850bc (opens in a new tab)
- https://git.kernel.org/stable/c/2ed3c9d955e8cd6361f130623baa664a75fb345f (opens in a new tab)
- https://git.kernel.org/stable/c/4606467a75cfc16721937272ed29462a750b60c8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-49112 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64534)Record last updated .