Skip to main content

Linux Kernel CVE-2025-68749

MEDIUM
Race Condition (CWE-362)
2025-12-24 416baaa9-dc9f-4396-8d5f-8c081fb06d67
4.7
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

Local driver race requiring specific Intel hardware, low privilege, high timing complexity, and purely availability impact with no confidentiality or integrity loss.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
3.3 LOW
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

1
Analysis Generated
Jul 30, 2026 - 08:41 vuln.today

DescriptionNVD

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().

AnalysisAI

Availability impact in the Linux kernel's Intel VPU accelerator driver (accel/ivpu) stems from a race condition between Buffer Object (BO) freeing and context teardown. A local, low-privileged user on a system with Intel VPU/NPU hardware can trigger the ivpu_gem_bo_free() path to remove a BO from the list before it is fully unmapped, causing file_priv_unbind() to encounter an unclean memory manager state and trigger a drm_mm_takedown() warning, ultimately resulting in a kernel availability impact. No public exploit exists and EPSS sits at the 1st percentile, indicating negligible real-world exploitation interest at this time.

Technical ContextAI

The affected component is the accel/ivpu subsystem, the Linux kernel driver for Intel's Visual Processing Unit (NPU/accelerator), present in newer Intel SoCs such as Meteor Lake. The vulnerability is classified as CWE-362 (Race Condition / Concurrent Execution Using Shared Resource with Improper Synchronization). The race exists between two execution paths: ivpu_gem_bo_free(), which removes a GEM Buffer Object from the bo_list prematurely, and file_priv_unbind(), which walks the bo_list during DRM context teardown and calls drm_mm_takedown(). Without proper locking, the memory manager can be left in an inconsistent state. The fix serializes the unmapping sequence with bo_list_lock to guarantee a BO is either fully unmapped at teardown or still present on the list for unbind to handle. Affected CPE: cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* (exact version bounds not specified in NVD CPE data).

RemediationAI

Apply the upstream kernel patches available at the four stable kernel git commits listed in the references. Distribution maintainers (Red Hat, Ubuntu, SUSE, Debian, etc.) are expected to backport these fixes into their stable kernel packages; check your distribution's security advisories for the specific package version that includes the fix. Until a patched kernel is deployed, a targeted workaround is to unload or blacklist the ivpu kernel module ('modprobe -r intel_vpu' or adding 'blacklist intel_vpu' to /etc/modprobe.d/) on systems where VPU/NPU acceleration is not required - this eliminates the attack surface at the cost of losing Intel NPU functionality for AI/ML inference workloads. Restricting unprivileged access to /dev/accel devices via udev rules or group permissions also reduces exposure by preventing low-privilege users from interacting with the driver, though it does not eliminate the vulnerability.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.0/base-os-container:latest Container suse/sl-micro/6.0/kvm-os-container:latest Container suse/sl-micro/6.0/rt-os-container:latest Image SL-Micro Affected
Container suse/sl-micro/6.0/toolbox:latest Affected
Image SLES-Azure-3P Image SLES-Azure-Basic Image SLES-Azure-Standard Image SLES-BYOS-Azure Image SLES-BYOS-EC2 Image SLES-BYOS-GCE Image SLES-CHOST-BYOS-Aliyun Image SLES-CHOST-BYOS-Azure Image SLES-CHOST-BYOS-EC2 Image SLES-CHOST-BYOS-GCE Image SLES-CHOST-BYOS-GDC Image SLES-CHOST-BYOS-SAP-CCloud Image SLES-EC2 Image SLES-EC2-ECS Image SLES-GCE Image SLES-GCE-3P Image SLES-Hardened-BYOS-Azure Image SLES-Hardened-BYOS-EC2 Image SLES-Hardened-BYOS-GCE Image SLES-SAPCAL-Azure Image SLES-SAPCAL-EC2 Image SLES-SAPCAL-GCE Affected
Image SLES-SAP-Azure Image SLES-SAP-Azure-3P Image SLES-SAP-BYOS-Azure Image SLES-SAP-BYOS-EC2 Image SLES-SAP-BYOS-GCE Image SLES-SAP-EC2 Image SLES-SAP-GCE Image SLES-SAP-GCE-3P Affected
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected

Share

CVE-2025-68749 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy