First published: Tue Jul 30 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | >=4.8<5.10.222 | |
Linux Linux kernel | >=5.11<5.15.163 | |
Linux Linux kernel | >=5.16<6.1.98 | |
Linux Linux kernel | >=6.2<6.6.39 | |
Linux Linux kernel | >=6.7<6.9.9 | |
Linux Linux kernel | =6.10-rc1 | |
redhat/kernel | <5.10.222 | 5.10.222 |
redhat/kernel | <5.15.163 | 5.15.163 |
redhat/kernel | <6.1.98 | 6.1.98 |
redhat/kernel | <6.6.39 | 6.6.39 |
redhat/kernel | <6.9.9 | 6.9.9 |
redhat/kernel | <6.10 | 6.10 |
debian/linux | 5.10.223-1 5.10.226-1 6.1.115-1 6.1.112-1 6.11.9-1 6.11.10-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.