Heimdall Security Logo

CVE-2024-42152

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.7%
Linux•Linux•Versions : <=6.1.*, <5502c1f1d0d7472706cc1f201aecf1c935d302d1, <b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5, 6.10, <818004f2a380420c19872171be716174d4985e33, 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a, 0, <c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4, 5.6, <=5.10.*, <=6.6.*, <940a71f08ef153ef807f751310b0648d1fa5d0da, <=6.9.*, 5.10.222, <2f3c22b1d3d7e86712253244797a651998c141fa, 6.9.9, <5.6, <=*, <=5.15.*, 5.15.163, 6.1.98, 6.6.39

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.

Gravité et risque d'exploitation

CVE-2024-42152 obtient un score CVSS de 7.5/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.73 %, ce qui la place devant 53.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <5502c1f1d0d7472706cc1f201aecf1c935d302d1, <b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5, 6.10, <818004f2a380420c19872171be716174d4985e33, 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a, 0, <c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4, 5.6, <=5.10.*, <=6.6.*, <940a71f08ef153ef807f751310b0648d1fa5d0da, <=6.9.*, 5.10.222, <2f3c22b1d3d7e86712253244797a651998c141fa, 6.9.9, <5.6, <=*, <=5.15.*, 5.15.163, 6.1.98, 6.6.39) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE