Answer in brief
CVE-2024-42152 records a High severity (CVSS 7.5) vulnerability in nvmet: fix a possible leak when destroy a ctrl during qp establishment. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a <2f3c22b1d3d7e86712253244797a651998c141fa || >=0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a <b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5 || >=0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a <940a71f08ef153ef807f751310b0648d1fa5d0da || >=0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a <5502c1f1d0d7472706cc1f201aecf1c935d302d1 || >=0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a <818004f2a380420c19872171be716174d4985e33 || >=0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a <c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4 | 2f3c22b1d3d7e86712253244797a651998c141fa, b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5, 940a71f08ef153ef807f751310b0648d1fa5d0da, 5502c1f1d0d7472706cc1f201aecf1c935d302d1, 818004f2a380420c19872171be716174d4985e33, c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Jul 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.