summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Mahoney <jeffm@suse.com>2016-07-05 17:32:30 -0400
committerJiri Slaby <jslaby@suse.cz>2016-07-18 13:52:16 +0200
commit114ffc5d2bbf3de6515d294edb9756a6fb35bd73 (patch)
treeb1baf741c158561ec72c6eb83e12679329d0eabc
parent22079c65db043d6440d2d00347556291dab779fc (diff)
downloadlwn-114ffc5d2bbf3de6515d294edb9756a6fb35bd73.tar.gz
lwn-114ffc5d2bbf3de6515d294edb9756a6fb35bd73.zip
ecryptfs: don't allow mmap when the lower fs doesn't support it
commit f0fe970df3838c202ef6c07a4c2b36838ef0a88b upstream. There are legitimate reasons to disallow mmap on certain files, notably in sysfs or procfs. We shouldn't emulate mmap support on file systems that don't offer support natively. CVE-2016-1583 Signed-off-by: Jeff Mahoney <jeffm@suse.com> [tyhicks: clean up f_op check by using ecryptfs_file_to_lower()] Signed-off-by: Tyler Hicks <tyhicks@canonical.com> Cc: Henry Jensen <hjensen@gmx.de> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
-rw-r--r--fs/ecryptfs/file.c15
1 files changed, 14 insertions, 1 deletions
diff --git a/fs/ecryptfs/file.c b/fs/ecryptfs/file.c
index f3fd66acae47..da02f7c16e0d 100644
--- a/fs/ecryptfs/file.c
+++ b/fs/ecryptfs/file.c
@@ -178,6 +178,19 @@ out:
return rc;
}
+static int ecryptfs_mmap(struct file *file, struct vm_area_struct *vma)
+{
+ struct file *lower_file = ecryptfs_file_to_lower(file);
+ /*
+ * Don't allow mmap on top of file systems that don't support it
+ * natively. If FILESYSTEM_MAX_STACK_DEPTH > 2 or ecryptfs
+ * allows recursive mounting, this will need to be extended.
+ */
+ if (!lower_file->f_op->mmap)
+ return -ENODEV;
+ return generic_file_mmap(file, vma);
+}
+
/**
* ecryptfs_open
* @inode: inode speciying file to open
@@ -353,7 +366,7 @@ const struct file_operations ecryptfs_main_fops = {
#ifdef CONFIG_COMPAT
.compat_ioctl = ecryptfs_compat_ioctl,
#endif
- .mmap = generic_file_mmap,
+ .mmap = ecryptfs_mmap,
.open = ecryptfs_open,
.flush = ecryptfs_flush,
.release = ecryptfs_release,