CVE-2026-64534Critical· 9.8▾ MidnightIn 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…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.4%
Last analysed / modified upstream
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().
Linux >= 91edfca6f8b364d60cde3ddefaf7d03ddf35774b < 22ec7a9fe9153d2737ee9b2fa6d2e43a1491decfLinux >= fda871c0ba5d2eed2cd1c881573168129da70058 < ba35b1c674ca3841c0dfadd698f2c1b3ec542d4eLinux >= fda871c0ba5d2eed2cd1c881573168129da70058 < c7874dad84b20433c0fe3919f291a762d40de08bLinux >= fda871c0ba5d2eed2cd1c881573168129da70058 < e602c93b25bda4a9d0ff1791a4bdbfdcbb074af1Linux >= fda871c0ba5d2eed2cd1c881573168129da70058 < d306da8833e75f669d93424fd84940236f3850bcLinux >= fda871c0ba5d2eed2cd1c881573168129da70058 < 2ed3c9d955e8cd6361f130623baa664a75fb345fLinux >= fda871c0ba5d2eed2cd1c881573168129da70058 < 4606467a75cfc16721937272ed29462a750b60c8Linux 4b17476d809273617d3317fa0d4ae78aa488d760Linux >= 5.10.20 < 5.10.261Linux >= 5.11.3 < 5.12Linux 5.12Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-38564High· 7.8bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
CVE-2026-99092Noneriscv: patch: fix handling of bpf-jit execmem addresses
CVE-2026-99089NoneASoC: samsung: i2s: enable op_clk in probe to balance runtime PM
CVE-2026-99093Nonemm: don't schedule deferred kernel page table freeing while booting
CVE-2026-99088Nonenet: openvswitch: validate transport header presence in set_ipv6_addr
CVE-2026-99090Nonedrm/amdgpu: serialize vblank counter reads against GPU reset