nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.12, 5.15.212, 6.1.178, 6.6.145, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 91edfca6f8b364d60cde3ddefaf7d03ddf35774b · fixed in 22ec7a9fe9153d2737ee9b2fa6d2e43a1491decf; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in ba35b1c674ca3841c0dfadd698f2c1b3ec542d4e; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in c7874dad84b20433c0fe3919f291a762d40de08b; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in e602c93b25bda4a9d0ff1791a4bdbfdcbb074af1; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in d306da8833e75f669d93424fd84940236f3850bc; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in 2ed3c9d955e8cd6361f130623baa664a75fb345f; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in 4606467a75cfc16721937272ed29462a750b60c8; From 5.10.20 · fixed in 5.10.261; From 5.11.3 · fixed in 5.12
- Linux Linux
5.12
- KernelLinux
fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.12.0 · fixed in 6.1.178; From 5.16.0 · fixed in 6.6.145; From 6.2.0 · fixed in 6.12.97; From 6.7.0 · fixed in 6.18.40
References 7
git.kernel.org
- stable/c/22ec7a9fe9153d2737ee9b2fa6d2e43a1491decf
- stable/c/ba35b1c674ca3841c0dfadd698f2c1b3ec542d4e
- stable/c/c7874dad84b20433c0fe3919f291a762d40de08b
- stable/c/e602c93b25bda4a9d0ff1791a4bdbfdcbb074af1
- stable/c/d306da8833e75f669d93424fd84940236f3850bc
- stable/c/2ed3c9d955e8cd6361f130623baa664a75fb345f
- stable/c/4606467a75cfc16721937272ed29462a750b60c8