nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.8epss 0.4%
exploitation probability
0.4%top 69% of all CVEs
observed exploitation
nono source reports it
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/22ec7a9fe9153d2737ee9b2fa6d2e43a1491decfhttps://git.kernel.org/stable/c/2ed3c9d955e8cd6361f130623baa664a75fb345fhttps://git.kernel.org/stable/c/4606467a75cfc16721937272ed29462a750b60c8https://git.kernel.org/stable/c/ba35b1c674ca3841c0dfadd698f2c1b3ec542d4ehttps://git.kernel.org/stable/c/c7874dad84b20433c0fe3919f291a762d40de08bhttps://git.kernel.org/stable/c/d306da8833e75f669d93424fd84940236f3850bchttps://git.kernel.org/stable/c/e602c93b25bda4a9d0ff1791a4bdbfdcbb074af1