CVE-2025-39896
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-01

Last updated on: 2025-12-12

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Prevent recovery work from being queued during device removal Use disable_work_sync() instead of cancel_work_sync() in ivpu_dev_fini() to ensure that no new recovery work items can be queued after device removal has started. Previously, recovery work could be scheduled even after canceling existing work, potentially leading to use-after-free bugs if recovery accessed freed resources. Rename ivpu_pm_cancel_recovery() to ivpu_pm_disable_recovery() to better reflect its new behavior.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-01
Last Modified
2025-12-12
Generated
2026-06-16
AI Q&A
2025-10-01
EPSS Evaluated
2026-06-15
NVD
CVE-2025-39896
Affected Vendors & Products
Showing 6 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.8 (inc) to 6.12.46 (exc)
linux linux_kernel From 6.13 (inc) to 6.16.6 (exc)
linux linux_kernel 6.17
linux linux_kernel 6.17
linux linux_kernel 6.17
linux linux_kernel 6.17
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's accel/ivpu component allowed recovery work to be queued even after device removal had started. The issue was that cancel_work_sync() was used, which canceled existing work but did not prevent new recovery work from being scheduled. This could lead to use-after-free bugs if recovery work accessed resources that had already been freed. The fix involved using disable_work_sync() to ensure no new recovery work can be queued during device removal.

Impact Analysis

This vulnerability can lead to use-after-free bugs, which may cause system instability, crashes, or potentially allow attackers to execute arbitrary code or cause denial of service by exploiting freed resources accessed during recovery work after device removal.

Mitigation Strategies

Update the Linux kernel to a version that includes the fix for this vulnerability, which prevents recovery work from being queued during device removal by using disable_work_sync() instead of cancel_work_sync() in ivpu_dev_fini(). This ensures no new recovery work items can be queued after device removal has started, avoiding use-after-free bugs.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-39896. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart