nvmet-tcp: Fix potential UAF when ddgst mismatch
- 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.265, 5.12, 5.15.216, 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: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 91edfca6f8b364d60cde3ddefaf7d03ddf35774b · fixed in dfb902462bca478f050224ec7a7195aafa7643b1; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in 7e558308eba14c8136cb1e615f0c850f76d1fc0a; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in 96fe2513df590e74b04253a45089cae75569570e; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in e091ff83d962f9ed00d9bd70443676de9fe98bdc; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in 6f9442983a3e4227afd1c83a5251ddbca585ea21; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in 088ee46c18d99baef453afd74181dd40ade044ad; From fda871c0ba5d2eed2cd1c881573168129da70058 · fixed in dbbd07d0a7020b80f6a7028e561908f7b83b3d5a; From 5.10.20 · fixed in 5.10.265; From 5.11.3 · fixed in 5.12
- Linux Linux
5.12
- KernelLinux
fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; 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/dfb902462bca478f050224ec7a7195aafa7643b1
- stable/c/7e558308eba14c8136cb1e615f0c850f76d1fc0a
- stable/c/96fe2513df590e74b04253a45089cae75569570e
- stable/c/e091ff83d962f9ed00d9bd70443676de9fe98bdc
- stable/c/6f9442983a3e4227afd1c83a5251ddbca585ea21
- stable/c/088ee46c18d99baef453afd74181dd40ade044ad
- stable/c/dbbd07d0a7020b80f6a7028e561908f7b83b3d5a