CVE-2025-37868 Details
Description
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 side is holding folio lock(s) and then interacting with the mappings of it, however those mappings are tied to some userptr, which means calling into the notifier callback and grabbing the notifier lock. With perfect timing it looks possible that the pages we pulled from the hmm fault can get sniped by migrate_pages_batch() at the same time that we are holding the notifier lock to mark the pages as accessed/dirty, but at this point we also want to grab the folio locks(s) to mark them as dirty, but if they are contended from notifier/migrate_pages_batch side then we deadlock since folio lock won't be dropped until we drop the notifier lock. Fortunately the mark_page_accessed/dirty is not really needed in the first place it seems and should have already been done by hmm fault, so just remove it. (cherry picked from commit bd7c0cb695e87c0e43247be8196b4919edbe0e85)
A deadlock vulnerability has been identified in the Linux kernel's Direct Rendering Manager (DRM) user pointer handling. The issue arises when the core kernel's page migration process holds locks on memory folios and simultaneously interacts with their mappings. These mappings are connected to user pointers, triggering notifier callbacks that require additional locking. This scenario can create a deadlock if the migration process and the notifier callback contend for folio locks at the same time. Fortunately, the notifier lock is not essential for marking pages as accessed or dirty, as this should have already been handled by the HMM fault. The vulnerability has been addressed by removing the unnecessary locking.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2577b202458cddff85cc154b1fe7f313e0d1f418 | kernel.org | Patch |
| https://git.kernel.org/stable/c/65dc4e3d5b01db0179fc95c1f0bdb87194c28ab5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/90574ecf6052be83971d91d16600c5cf07003bbb | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12.19, < 6.12.25 >= 6.13.7, < 6.14 >= 6.14.1, < 6.14.4 6.14 - 6.14 rc6 6.14 rc7 6.15 rc1 6.15 rc2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 12, 2025 | Initial Analysis | [email protected] |
| May 9, 2025 | New CVE Received | kernel.org |