CVE-2024-26846nvme-fc: do not wait in vain when unloading module
- 4.4MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 58 days later
· 58 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Analyzed | 3.1 | Medium4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.4.
Affected products
- affected 4c73cbdff1119d088ed16d63def59ad32b11b18f – < 4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2
- affected 4c73cbdff1119d088ed16d63def59ad32b11b18f – < 0bf567d6d9ffe09e059bbdfb4d07143cef42c75c
- affected 4c73cbdff1119d088ed16d63def59ad32b11b18f – < 085195aa90a924c79e35569bcdad860d764a8e17
- affected 4c73cbdff1119d088ed16d63def59ad32b11b18f – < baa6b7eb8c66486bd64608adc63fe03b30d3c0b9
- affected 4c73cbdff1119d088ed16d63def59ad32b11b18f – < c0882c366418bf9c19e1ba7f270fe377a9bf5d67
- affected 4c73cbdff1119d088ed16d63def59ad32b11b18f – < 70fbfc47a392b98e5f8dba70c6efc6839205c982
- affected 5.3
- unaffected < 5.3
- unaffected 5.10.211 – ≤ 5.10.*
- unaffected 5.15.150 – ≤ 5.15.*
- unaffected 6.1.80 – ≤ 6.1.*
- unaffected 6.6.19 – ≤ 6.6.*
- unaffected 6.7.7 – ≤ 6.7.*
- unaffected 6.8 – ≤ *
References
References7
- https://git.kernel.org/stable/c/4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0bf567d6d9ffe09e059bbdfb4d07143cef42c75c (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/085195aa90a924c79e35569bcdad860d764a8e17 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/baa6b7eb8c66486bd64608adc63fe03b30d3c0b9 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/c0882c366418bf9c19e1ba7f270fe377a9bf5d67 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/70fbfc47a392b98e5f8dba70c6efc6839205c982 (opens in a new tab)x_transferred
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-24108 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-26846)Record last updated .