CVE-2024-42152
nvmet: fix a possible leak when destroy a ctrl during qp establishment
Reported by linux · Published July 30, 2024
In the Linux kernel, the following vulnerability has been resolved: nvmet: fix a possible leak when destroy a ctrl during qp establishment In nvmet_sq_destroy we capture sq->ctrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl->sqs and sq->ctrl (for nvme-loop primarily), and drop the final reference on the ctrl. However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But *before* kill_and_confirm of sq->ref (i.e. the admin connect managed to get an sq live reference). In this case, sq->ctrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl. Solve this by re-capturing the sq->ctrl after all inflight request has completed, where for sure sq->ctrl reference is final, and move forward based on that. This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.9.9, 6.6.39, 6.1.98, 5.15.163, 5.10.222 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a, 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a, 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a |
| Linux | Linux | 5.6, 0, 5.10.222 |
| linux | linux_kernel | 5.6, 5.6, 5.6 |
| Linux | Linux | 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a, 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a, 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a |
Timeline
- Jul 29, 2024 CVE Published
- Jul 30, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (6 in total, the first dated here)
- Jan 6, 2026 Security Advisory (357 in total, the first dated here)
- Jan 6, 2026 CVE Updated
- Mar 30, 2026 Distribution Patch (239 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-42152
vulnetix vdb fixes CVE-2024-42152
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-42152/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart