diff options
| author | Suren Baghdasaryan <surenb@google.com> | 2020-01-27 15:56:16 -0800 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2020-04-28 19:03:39 +0100 |
| commit | 85216b0a3fc5f3eb08e68750175f8507d5608e37 (patch) | |
| tree | 3d76ba704cff4546089fe4cdd040d2868255408f /net | |
| parent | 4af47d3cc875e43a523f6d3b3edef2ca785ccf27 (diff) | |
| download | linux-stable-85216b0a3fc5f3eb08e68750175f8507d5608e37.tar.gz linux-stable-85216b0a3fc5f3eb08e68750175f8507d5608e37.tar.bz2 linux-stable-85216b0a3fc5f3eb08e68750175f8507d5608e37.zip | |
staging: android: ashmem: Disallow ashmem memory from being remapped
commit 6d67b0290b4b84c477e6a2fc6e005e174d3c7786 upstream.
When ashmem file is mmapped, the resulting vma->vm_file points to the
backing shmem file with the generic fops that do not check ashmem
permissions like fops of ashmem do. If an mremap is done on the ashmem
region, then the permission checks will be skipped. Fix that by disallowing
mapping operation on the backing shmem file.
Reported-by: Jann Horn <jannh@google.com>
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Todd Kjos <tkjos@google.com>
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Link: https://lore.kernel.org/r/20200127235616.48920-1-tkjos@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions