CVE-2025-39945cnic: Fix use-after-free bugs in cnic_delete_task
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% 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: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (cleanup) | CPU 1 (delayed work callback) cnic_netdev_event() | cnic_stop_hw() | cnic_delete_task() cnic_cm_stop_bnx2x_hw() | ... cancel_delayed_work() | /* the queue_delayed_work() flush_workqueue() | executes after flush_workqueue()*/ | queue_delayed_work() cnic_free_dev(dev)//free | cnic_delete_task() //new instance | dev = cp->dev; //use Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the cyclic delayed work item is properly canceled and that any ongoing execution of the work item completes before the cnic_dev is deallocated. Furthermore, since cancel_delayed_work_sync() uses __flush_work(work, true) to synchronously wait for any currently executing instance of the work item to finish, the flush_workqueue() becomes redundant and should be removed. This bug was identified through static analysis. To reproduce the issue and validate the fix, I simulated the cnic PCI device in QEMU and introduced intentional delays — such as inserting calls to ssleep() within the cnic_delete_task() function — to increase the likelihood of triggering the bug.
Timeline
ID reserved
By Linux
- 6 months later
· 6 months later
Published
- 10 months later
· 10 months 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 |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected fdf24086f4752aee5dfb40143c736250df017820 – < fde6e73189f40ebcf0633aed2b68e731c25f3aa3
- affected fdf24086f4752aee5dfb40143c736250df017820 – < 7b6a5b0a6b392263c3767fc945b311ea04b34bbd
- affected fdf24086f4752aee5dfb40143c736250df017820 – < 0405055930264ea8fd26f4131466fa7652e5e47d
- affected fdf24086f4752aee5dfb40143c736250df017820 – < e1fcd4a9c09feac0902a65615e866dbf22616125
- affected fdf24086f4752aee5dfb40143c736250df017820 – < 8eeb2091e72d75df8ceaa2172638d61b4cf8929a
- affected fdf24086f4752aee5dfb40143c736250df017820 – < 6e33a7eed587062ca8161ad1f4584882a860d697
- affected fdf24086f4752aee5dfb40143c736250df017820 – < 0627e1481676669cae2df0d85b5ff13e7d24c390
- affected fdf24086f4752aee5dfb40143c736250df017820 – < cfa7d9b1e3a8604afc84e9e51d789c29574fb216
- affected 2.6.37
- unaffected < 2.6.37
- unaffected 5.4.300 – ≤ 5.4.*
- unaffected 5.10.245 – ≤ 5.10.*
- unaffected 5.15.194 – ≤ 5.15.*
- unaffected 6.1.154 – ≤ 6.1.*
- unaffected 6.6.108 – ≤ 6.6.*
- unaffected 6.12.49 – ≤ 6.12.*
- unaffected 6.16.9 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References8
- https://git.kernel.org/stable/c/fde6e73189f40ebcf0633aed2b68e731c25f3aa3 (opens in a new tab)
- https://git.kernel.org/stable/c/7b6a5b0a6b392263c3767fc945b311ea04b34bbd (opens in a new tab)
- https://git.kernel.org/stable/c/0405055930264ea8fd26f4131466fa7652e5e47d (opens in a new tab)
- https://git.kernel.org/stable/c/e1fcd4a9c09feac0902a65615e866dbf22616125 (opens in a new tab)
- https://git.kernel.org/stable/c/8eeb2091e72d75df8ceaa2172638d61b4cf8929a (opens in a new tab)
- https://git.kernel.org/stable/c/6e33a7eed587062ca8161ad1f4584882a860d697 (opens in a new tab)
- https://git.kernel.org/stable/c/0627e1481676669cae2df0d85b5ff13e7d24c390 (opens in a new tab)
- https://git.kernel.org/stable/c/cfa7d9b1e3a8604afc84e9e51d789c29574fb216 (opens in a new tab)
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-2025-32391 (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-2025-39945)Record last updated .