{"id":"CVE-2025-39896","state":"PUBLISHED","title":"accel/ivpu: Prevent recovery work from being queued during device removal","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Prevent recovery work from being queued during device removal\n\nUse disable_work_sync() instead of cancel_work_sync() in ivpu_dev_fini()\nto ensure that no new recovery work items can be queued after device\nremoval has started. Previously, recovery work could be scheduled even\nafter canceling existing work, potentially leading to use-after-free\nbugs if recovery accessed freed resources.\n\nRename ivpu_pm_cancel_recovery() to ivpu_pm_disable_recovery() to better\nreflect its new behavior.","publishedAt":"2025-10-01T07:42:44.714Z","updatedAt":"2026-08-05T12:05:57.549Z","severity":{"score":7.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"58cde80f45a2b1683ea3c24a9a9a4b0e1005336b","status":"affected","lessThan":"54c49eca38dbd06913a696f6d7610937dcfad226","versionType":"git"},{"version":"58cde80f45a2b1683ea3c24a9a9a4b0e1005336b","status":"affected","lessThan":"565d2c15b6c36c3250e694f7b9a86229c1787be5","versionType":"git"},{"version":"58cde80f45a2b1683ea3c24a9a9a4b0e1005336b","status":"affected","lessThan":"69a79ada8eb034ce016b5b78fb7d08d8687223de","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/ivpu/ivpu_drv.c","drivers/accel/ivpu/ivpu_pm.c","drivers/accel/ivpu/ivpu_pm.h"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.8","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.8","versionType":"semver"},{"version":"6.12.46","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.16.6","status":"unaffected","lessThanOrEqual":"6.16.*","versionType":"semver"},{"version":"6.17","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/ivpu/ivpu_drv.c","drivers/accel/ivpu/ivpu_pm.c","drivers/accel/ivpu/ivpu_pm.h"]}],"references":["https://git.kernel.org/stable/c/54c49eca38dbd06913a696f6d7610937dcfad226","https://git.kernel.org/stable/c/565d2c15b6c36c3250e694f7b9a86229c1787be5","https://git.kernel.org/stable/c/69a79ada8eb034ce016b5b78fb7d08d8687223de"],"weaknesses":["CWE-416"],"ingestedAt":"2026-10-29T20:09:09.358Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2025/39xxx/CVE-2025-39896.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-39896","state":"PUBLISHED","datePublished":"2025-10-01T07:42:44.714Z","dateUpdated":"2026-08-05T12:05:57.549Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2025-04-16T07:20:57.146Z"},"containers":{"cna":{"title":"accel/ivpu: Prevent recovery work from being queued during device removal","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Prevent recovery work from being queued during device removal\n\nUse disable_work_sync() instead of cancel_work_sync() in ivpu_dev_fini()\nto ensure that no new recovery work items can be queued after device\nremoval has started. Previously, recovery work could be scheduled even\nafter canceling existing work, potentially leading to use-after-free\nbugs if recovery accessed freed resources.\n\nRename ivpu_pm_cancel_recovery() to ivpu_pm_disable_recovery() to better\nreflect its new behavior."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"58cde80f45a2b1683ea3c24a9a9a4b0e1005336b","status":"affected","lessThan":"54c49eca38dbd06913a696f6d7610937dcfad226","versionType":"git"},{"version":"58cde80f45a2b1683ea3c24a9a9a4b0e1005336b","status":"affected","lessThan":"565d2c15b6c36c3250e694f7b9a86229c1787be5","versionType":"git"},{"version":"58cde80f45a2b1683ea3c24a9a9a4b0e1005336b","status":"affected","lessThan":"69a79ada8eb034ce016b5b78fb7d08d8687223de","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/ivpu/ivpu_drv.c","drivers/accel/ivpu/ivpu_pm.c","drivers/accel/ivpu/ivpu_pm.h"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.8","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.8","versionType":"semver"},{"version":"6.12.46","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.16.6","status":"unaffected","lessThanOrEqual":"6.16.*","versionType":"semver"},{"version":"6.17","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/ivpu/ivpu_drv.c","drivers/accel/ivpu/ivpu_pm.c","drivers/accel/ivpu/ivpu_pm.h"]}],"references":[{"url":"https://git.kernel.org/stable/c/54c49eca38dbd06913a696f6d7610937dcfad226"},{"url":"https://git.kernel.org/stable/c/565d2c15b6c36c3250e694f7b9a86229c1787be5"},{"url":"https://git.kernel.org/stable/c/69a79ada8eb034ce016b5b78fb7d08d8687223de"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The Intel NPU is an integrated PCI device driven through local ioctls on /dev/accel/accel0 and local sysfs/module operations; there is no network or adjacent-network path into ivpu_pm_trigger_recovery() or ivpu_dev_fini().\nAC:L - The attacker fully controls the recovery-triggering side of the race and can arm it persistently — wedging the NPU firmware makes every subsequent JSM/IPC message time out, so once teardown starts, `ivpu_pm_trigger_recovery()` fires from context_abort_work, IRQ handlers, or IPC timeouts with near-certainty rather than as a low-probability window, and the attempt can be repeated indefinitely at no cost.\nPR:L - Reaching the recovery triggers only needs an open handle to the accel render node — all ivpu ioctls are declared with flags 0 (no DRM_ROOT_ONLY/DRM_AUTH), so any local user in the render/uaccess group can submit faulting jobs and hang the firmware.\nUI:N - No victim must open attacker-supplied content or perform an interactive action; device teardown also occurs from automated events such as package-driven driver reload, PCI error handling, and shutdown/unbind scripts.\nS:U - The use-after-free corrupts kernel-managed driver structures within the same security authority; there is no crossing of a VM, IOMMU, or sandbox boundary.\nC:H - The late-running recovery worker reads freed drmm/GEM allocations (fw->mem, ipc->mem_tx/rx, a destroyed context_xa) and drives ivpu_dev_coredump()/ivpu_jsm_state_dump() over them, and a freed-then-reallocated work_struct yields a controllable dispatch — usable for arbitrary kernel memory disclosure.\nI:H - ivpu_ipc_reset() memsets and ivpu_fw_load() memcpys directly into buffer objects already released by ivpu_ipc_fini()/ivpu_fw_mem_fini(), writing into freed pages that can be reallocated to other kernel objects; the freed work->func dereference additionally gives control-flow hijack potential.\nA:H - The use-after-free reliably produces a kernel oops or panic — NULL/freed ivpu_bo_vaddr() dereferences, iteration of a destroyed xarray, and MMIO access to a powered-down D3hot device — taking down the whole system."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T12:05:57.549Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.12.46"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.16.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.8","versionEndExcluding":"6.17"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"cvssV3_1":{"scope":"UNCHANGED","version":"3.1","baseScore":7.8,"attackVector":"LOCAL","baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","integrityImpact":"HIGH","userInteraction":"NONE","attackComplexity":"LOW","availabilityImpact":"HIGH","privilegesRequired":"LOW","confidentialityImpact":"HIGH"}},{"other":{"type":"ssvc","content":{"id":"CVE-2025-39896","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"version":"2.0.3","timestamp":"2026-01-14T19:28:28.158447Z"}}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-416","lang":"en","type":"CWE","description":"CWE-416 Use After Free"}]}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-01-14T19:33:13.870Z"}}]}}}