userfaultfd: fix a race between writeprotect and exit_mmap()
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 |
|
|
5.10.765.14.155.15In the Linux kernel, the following vulnerability has been resolved:
userfaultfd: fix a race between writeprotect and exit_mmap()
A race is possible when a process exits, its VMAs are removed by exit_mmap() and at the same time userfaultfd_writeprotect() is called.
The race was detected by KASAN on a development kernel, but it appears to be possible on vanilla kernels as well.
Use mmget_not_zero() to prevent the race as done in other userfaultfd operations.
From the CVE record · Linux
The Linux kernel has a race between userfaultfd_writeprotect() and exit_mmap() when a process exits while write protection is being applied. A local process may trigger this race; the input does not specify authentication requirements, user interaction, or a resulting impact.
Engineers running the Linux kernel should check their kernel version; affected versions are not specified.