In the Linux kernel, the following vulnerability has been resolved: userfaultfd: release page in error path to avoid BUGON Consider the following sequence of events: 1. Userspace issues a UFFD ioctl, which ends up calling into shmemmfillatomicpte(). We successfully account the blocks, we shmemallocpage(), but then the copyfromuser() fails. We return -ENOENT. We don't release the page we allocated. 2. Our caller detects this error code, tries the copyfromuser() after dropping the mmaplock, and retries, calling back into shmemmfillatomicpte(). 3. Meanwhile, let's say another process filled up the tmpfs being used. 4. So shmemmfillatomicpte() fails to account blocks this time, and immediately returns - without releasing the page. This triggers a BUGON in our caller, which asserts that the page should always be consumed, unless -ENOENT is returned. To fix this, detect if we have such a "dangling" page when accounting fails, and if so, release it before returning.