diff options
author | Todd Kjos <tkjos@android.com> | 2019-03-01 15:06:06 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-03-21 06:51:32 +0100 |
commit | 5cec2d2e5839f9c0fec319c523a911e0a7fd299f (patch) | |
tree | 84da718fce8d1beaecc8ac62c419f95da174db54 /certs | |
parent | 5997da82145bb7c9a56d834894cb81f81f219344 (diff) | |
download | linux-5cec2d2e5839f9c0fec319c523a911e0a7fd299f.tar.bz2 |
binder: fix race between munmap() and direct reclaim
An munmap() on a binder device causes binder_vma_close() to be called
which clears the alloc->vma pointer.
If direct reclaim causes binder_alloc_free_page() to be called, there
is a race where alloc->vma is read into a local vma pointer and then
used later after the mm->mmap_sem is acquired. This can result in
calling zap_page_range() with an invalid vma which manifests as a
use-after-free in zap_page_range().
The fix is to check alloc->vma after acquiring the mmap_sem (which we
were acquiring anyway) and skip zap_page_range() if it has changed
to NULL.
Signed-off-by: Todd Kjos <tkjos@google.com>
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions