https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 11:51:40 +0000 https://cve.radiocsirt.org/vuln/cve-2024-26846 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvme-fc: do not wait in vain when unloading module</p> <p>The module exit path has race between deleting all controllers and freeing &#39;left over IDs&#39;. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit.</p> <p>There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever.</p> <p>If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue.</p> <p>While at it, remove the unused nvme_fc_wq workqueue too.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nvme-fc: do not wait in vain when unloading module</p> <p>The module exit path has race between deleting all controllers and freeing &#39;left over IDs&#39;. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit.</p> <p>There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever.</p> <p>If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue.</p> <p>While at it, remove the unused nvme_fc_wq workqueue too.</p> https://cve.radiocsirt.org/vuln/cve-2024-26846