nvmet-tcp: Fix potential UAF when ddgst mismatch
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 5.10.265, Kernel 5.15.216, Kernel 6.1.178 and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.10.20 <5.10.265, >=5.11.3 <5.15.216, >=5.16 <6.1.178, >=6.13 <6.18.40, >=6.19 <7.1, >=6.2 <6.6.145, >=6.7 <6.12.97, =7.1, >=91edfca6f8b364d60cde3ddefaf7d03ddf35774b <dfb902462bca478f050224ec7a7195aafa7643b1, >=fda871c0ba5d2eed2cd1c881573168129da70058 <088ee46c18d99baef453afd74181dd40ade044ad, >=fda871c0ba5d2eed2cd1c881573168129da70058 <6f9442983a3e4227afd1c83a5251ddbca585ea21, >=fda871c0ba5d2eed2cd1c881573168129da70058 <7e558308eba14c8136cb1e615f0c850f76d1fc0a, >=fda871c0ba5d2eed2cd1c881573168129da70058 <96fe2513df590e74b04253a45089cae75569570e, >=fda871c0ba5d2eed2cd1c881573168129da70058 <dbbd07d0a7020b80f6a7028e561908f7b83b3d5a, >=fda871c0ba5d2eed2cd1c881573168129da70058 <e091ff83d962f9ed00d9bd70443676de9fe98bdc, =4b17476d809273617d3317fa0d4ae78aa488d760, =5.12, >=5.11.3 <5.12 | 5.10.265, 5.15.216, 6.1.178, 6.18.40, 7.1, 6.6.145, 6.12.97, dfb902462bca478f050224ec7a7195aafa7643b1, 088ee46c18d99baef453afd74181dd40ade044ad, 6f9442983a3e4227afd1c83a5251ddbca585ea21, 7e558308eba14c8136cb1e615f0c850f76d1fc0a, 96fe2513df590e74b04253a45089cae75569570e, dbbd07d0a7020b80f6a7028e561908f7b83b3d5a, e091ff83d962f9ed00d9bd70443676de9fe98bdc, 5.12 |
| linux-kernel: Kernel | >=5.10.20 <5.10.265, >=5.11.3 <5.12, >=5.12.0 <5.15.216, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97 | 5.10.265, 5.12, 5.15.216, 6.1.178, 6.18.40, 6.6.145, 6.12.97 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket