CVE-2024-26846: Linux kernel · nvme-fc: do not wait in vain when unloading module
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 4.4 Medium · fixed in 5.15.0-1063.69~20.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 10:59 UTC
- Patch
- Available – fixed in 5.15.0-1063.69~20.04.1, 5.15.0-1065.74~20.04.1, 5.15.0-1062.70~20.04.1 +33
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6820-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6871-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6892-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro Realtime 24.04 LTSlinux-raspi-realtimepkg:deb/ubuntu/linux-raspi-realtime?arch=source&distro=realtime/nobleOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-allwinner-5.19pkg:deb/ubuntu/linux-allwinner-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-aws-5.19pkg:deb/ubuntu/linux-aws-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-aws-6.2pkg:deb/ubuntu/linux-aws-6.2?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2024-26846 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-26846 (opens in a new tab)
- git.kernel.org/linus/70fbfc47a392b98e5f8dba70c6efc6839205c982 (opens in a new tab)
- git.kernel.org/stable/c/4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2 (opens in a new tab)
- git.kernel.org/stable/c/0bf567d6d9ffe09e059bbdfb4d07143cef42c75c (opens in a new tab)
- git.kernel.org/stable/c/085195aa90a924c79e35569bcdad860d764a8e17 (opens in a new tab)
- git.kernel.org/stable/c/baa6b7eb8c66486bd64608adc63fe03b30d3c0b9 (opens in a new tab)
- git.kernel.org/stable/c/c0882c366418bf9c19e1ba7f270fe377a9bf5d67 (opens in a new tab)
- git.kernel.org/stable/c/70fbfc47a392b98e5f8dba70c6efc6839205c982 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6871-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6892-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)