CVE-2025-68749
Unknown Unknown - Not Provided
Race Condition in Linux Kernel IVPU BO Unbinding Causes Memory Leak

Publication date: 2025-12-24

Last updated on: 2026-02-26

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix race condition when unbinding BOs Fix 'Memory manager not clean during takedown' warning that occurs when ivpu_gem_bo_free() removes the BO from the BOs list before it gets unmapped. Then file_priv_unbind() triggers a warning in drm_mm_takedown() during context teardown. Protect the unmapping sequence with bo_list_lock to ensure the BO is always fully unmapped when removed from the list. This ensures the BO is either fully unmapped at context teardown time or present on the list and unmapped by file_priv_unbind().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2026-02-26
Generated
2026-06-16
AI Q&A
2025-12-24
EPSS Evaluated
2026-06-15
NVD
CVE-2025-68749
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.13 (inc) to 6.17.13 (exc)
linux linux_kernel From 6.18 (inc) to 6.18.2 (exc)
linux linux_kernel From 6.8 (inc) to 6.12.68 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in the Linux kernel's accel/ivpu component related to unbinding buffer objects (BOs). Specifically, when ivpu_gem_bo_free() removes a BO from the BOs list before it is unmapped, it can cause a 'Memory manager not clean during takedown' warning. The issue arises because file_priv_unbind() then triggers a warning during context teardown in drm_mm_takedown(). The fix involves protecting the unmapping sequence with a lock (bo_list_lock) to ensure the BO is fully unmapped when removed from the list, preventing the race condition.

Impact Analysis

This vulnerability can lead to warnings and potential instability during the teardown of contexts in the Linux kernel's memory management for the ivpu accelerator. It may cause improper cleanup of memory mappings, which could result in resource leaks or unexpected behavior in systems relying on this component. However, no direct security impact such as privilege escalation or data corruption is described.

Mitigation Strategies

Apply the patch or update to the fixed version of the Linux kernel that resolves the race condition in the accel/ivpu component by protecting the unmapping sequence with bo_list_lock. This ensures proper cleanup during context teardown and prevents the 'Memory manager not clean during takedown' warning.

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