CVE-2025-37868: drm/xe/userptr: fix notifier vs folio deadlock

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-05-09 · updated 2026-06-17
Weakness: CWE-667

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)

Affected products

Linux kernel: from 6.12.19 before 6.12.25; from 6.13.7 before 6.14; from 6.14.1 before 6.14.4; 6.14, 6.14-rc6, 6.14-rc7, 6.15-rc1, 6.15-rc2 — fixed in 6.12.25, 6.14, 6.14.4

How to fix

Upgrade to a fixed version: Linux kernel 6.12.25, 6.14, 6.14.4. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-37868 or the next vulnerability affects your stack