A flaw in the Linux kernel’s DRM pagemap handling allows a device‑private folio that has been migrated to system memory to be migrated again before the migration is finalized. The duplicate migration leaves an uncharged folio on the LRU list, causing the folio_lruvec_lock_irqsave function to retry indefinitely. This reduces the kernel to a state of soft lockup and RCU stall, effectively denying service to any process that relies on the affected CPU core.

The vulnerability affects the Linux kernel across all distributions that compile the DRM subsystem. No specific kernel version boundary is listed in the data, so any kernel config that includes the DRM pagemap code and device‑private folio migration path could be impacted until the patch that marks migrated folios is applied.

External exploit probability data is not available and the vulnerability is not listed in CISA’s KEV catalog. The severity is high because a soft lockup can intentionally halt application performance or service availability. The attack vector is not explicitly defined in the description; however, the incident logs indicate it can be triggered by kernel paths handling device‑private folios, suggesting that a privileged attacker or a compromised kernel module could exploit the flaw. In the absence of more detailed metrics, the risk is considered significant for systems that do not apply the patch.