CVE-2024-42152: Linux kernel · nvmet: fix a possible leak when destroy a ctrl during qp establishment
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 5.15.0-1069.75~20.04.1 : patch Linux kernel soon.
Data as of 26 Oct 2026, 23:28 UTC
- Patch
- Available – fixed in 5.15.0-1069.75~20.04.1, 5.15.0-1072.81~20.04.1, 5.15.0-1068.76~20.04.1 +54
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7009-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7019-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7009-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkeoppkg:deb/ubuntu/linux-gkeop?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2024-42152 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-42152 (opens in a new tab)
- git.kernel.org/linus/c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4 (opens in a new tab)
- git.kernel.org/stable/c/2f3c22b1d3d7e86712253244797a651998c141fa (opens in a new tab)
- git.kernel.org/stable/c/b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5 (opens in a new tab)
- git.kernel.org/stable/c/940a71f08ef153ef807f751310b0648d1fa5d0da (opens in a new tab)
- git.kernel.org/stable/c/5502c1f1d0d7472706cc1f201aecf1c935d302d1 (opens in a new tab)
- git.kernel.org/stable/c/818004f2a380420c19872171be716174d4985e33 (opens in a new tab)
- git.kernel.org/stable/c/c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7009-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7019-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7009-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)