Deadlock Vulnerability in Linux Kernel's DRM Userptr Handling

linux Updated 02 Oct 2025

Summary

09/05/2025
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2025-37868: In the Linux kernel, the following vulnerability has been resolved: drm/xe/userptr: fix notifier vs folio deadlock User is reporting what smells like notifier vs folio deadlock, where migrate_pages_batch() on core kernel... Affects linux versions < 6.12.25-1. Fixed in 6.12.25-1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Linux kernel is a core component of many operating systems, providing essential services for hardware management, process control, and system security. The 'linux' package in Debian distributions serves as the foundation for these systems, enabling the execution of applications and management of system resources. This vulnerability specifically affects the DRM (Direct Rendering Manager) subsystem, which is responsible for interfacing with GPUs and managing graphics rendering. The issue arises from a potential deadlock scenario when handling user pointers, which can lead to system instability and performance degradation.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified in the DRM subsystem related to user pointer handling. The issue stems from a deadlock that can occur when the migrate_pages_batch() function interacts with folio locks while simultaneously holding a notifier lock. This situation can lead to a scenario where the system becomes unresponsive, as the folio lock cannot be released until the notifier lock is dropped. The vulnerability was introduced in earlier versions of the kernel and has been addressed in the fixed version. The technical details indicate that the mark_page_accessed/dirty function is unnecessary in this context and can be safely removed to prevent the deadlock.

How To Fix

Minimum fixed version

6.12.25-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. It is recommended to apply the patch as soon as it is available to mitigate the risk of encountering the deadlock scenario.

Conclusion

The identified deadlock vulnerability in the Linux kernel's DRM subsystem poses a risk to system stability. Users are advised to update their 'linux' package to the fixed version 6.12.25-1 to mitigate this issue. Regular monitoring for vulnerabilities using tools like Vulert can help maintain system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

The vulnerability is a potential deadlock in the Linux kernel's DRM subsystem when handling user pointers, which can lead to system instability.

You can use tools like Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

Failure to address this vulnerability may result in system crashes or unresponsiveness, particularly during graphics operations.

Yes, updating to version 6.12.25-1 or later will resolve the vulnerability.

While manual patching is possible, it is recommended to update to the patched version to ensure all related issues are addressed.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.12.25-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback