In the Linux kernel, the following vulnerability has been resolved:

nvme-fc: do not wait in vain when unloading module

The module exit path has race between deleting all controllers and
freeing 'left over IDs'. To prevent double free a synchronization
between nvme_delete_ctrl and ida_destroy has been added by the initial
commit.

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.

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.

While at it, remove the unused nvme_fc_wq workqueue too.

kernel.org https://git.kernel.org/stable/c/085195aa90a924c79e35569bcdad860d764a8e17 [No types assigned]

kernel.org https://git.kernel.org/stable/c/0bf567d6d9ffe09e059bbdfb4d07143cef42c75c [No types assigned]

kernel.org https://git.kernel.org/stable/c/4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2 [No types assigned]

kernel.org https://git.kernel.org/stable/c/70fbfc47a392b98e5f8dba70c6efc6839205c982 [No types assigned]

kernel.org https://git.kernel.org/stable/c/baa6b7eb8c66486bd64608adc63fe03b30d3c0b9 [No types assigned]

kernel.org https://git.kernel.org/stable/c/c0882c366418bf9c19e1ba7f270fe377a9bf5d67 [No types assigned]