nvmet-tcp: Fix potential UAF when ddgst mismatch
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fda871c0ba5d2eed2cd1c881573168129da70058 · < 088ee46c18d99baef453afd74181dd40ade044ad| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s nvmet-tcp digest error handling can release a command’s submission-queue reference twice. This can occur on an NVMe/TCP connection with data digest enabled when a digest mismatch affects a non-final H2C_DATA PDU during an R2T-based transfer, followed by queue teardown. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with nvmet-tcp should check their versions; affected versions are not specified in the input.