Linux kernel denial of service in userfaultfd unregistration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm/userfaultfd: write-lock the VMA before waking waiters when unregistering
userfaultfd_unregister() wakes pending missing faults before clearing the VMA's userfaultfd registration. With per-VMA fault locking, holding mmap_lock for write does not prevent another fault from queuing after the wakeup but before userfaultfd_clear_vma() write-locks the VMA. That waiter can then remain asleep indefinitely.
Call vma_start_write() before waking waiters. Existing fault handlers queue themselves before dropping the VMA read lock, and new readers are excluded until mmap_write_unlock().
From the CVE record · Linux
In the Linux kernel, unregistering a userfaultfd can wake pending missing-fault waiters before clearing the VMA’s registration. With per-VMA fault locking, another fault can queue between those operations and remain asleep indefinitely. The input does not establish an attacker scenario or authentication requirements.
Engineers running Linux kernels with per-VMA fault locking and userfaultfd use should check their deployments; affected versions were not provided.