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.
Published 2024-04-17 10:15:10
Updated 2024-04-17 12:48:08
Source Linux
View at NVD,
Vulnerability category: Memory Corruption

Exploit prediction scoring system (EPSS) score for CVE-2024-26846

Probability of exploitation activity in the next 30 days EPSS Score History
~ 9 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2024-26846

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
RedHat-CVE-2024-26846 2024-04-17

References for CVE-2024-26846

Products affected by CVE-2024-26846

The following product & version information is provided by We provide product & version information for most CVEs even if they are not available from NVD.
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to terms of use!