You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Eric W. Biederman 7f78e03513 fs: Limit sys_mount to only request filesystem modules. ... Modify the request_module to prefix the file system type with "fs-" and add aliases to all of the filesystems that can be built as modules to match. A common practice is to build all of the kernel code and leave code that is not commonly needed as modules, with the result that many users are exposed to any bug anywhere in the kernel. Looking for filesystems with a fs- prefix limits the pool of possible modules that can be loaded by mount to just filesystems trivially making things safer with no real cost. Using aliases means user space can control the policy of which filesystem modules are auto-loaded by editing /etc/modprobe.d/*.conf with blacklist and alias directives. Allowing simple, safe, well understood work-arounds to known problematic software. This also addresses a rare but unfortunate problem where the filesystem name is not the same as it's module name and module auto-loading would not work. While writing this patch I saw a handful of such cases. The most significant being autofs that lives in the module autofs4. This is relevant to user namespaces because we can reach the request module in get_fs_type() without having any special permissions, and people get uncomfortable when a user specified string (in this case the filesystem type) goes all of the way to request_module. After having looked at this issue I don't think there is any particular reason to perform any filtering or permission checks beyond making it clear in the module request that we want a filesystem module. The common pattern in the kernel is to call request_module() without regards to the users permissions. In general all a filesystem module does once loaded is call register_filesystem() and go to sleep. Which means there is not much attack surface exposed by loading a filesytem module unless the filesystem is mounted. In a user namespace filesystems are not mounted unless .fs_flags = FS_USERNS_MOUNT, which most filesystems do not set today. Acked-by: Serge Hallyn <serge.hallyn@canonical.com> Acked-by: Kees Cook <keescook@chromium.org> Reported-by: Kees Cook <keescook@google.com> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>		12 years ago
..
Kconfig	…
Makefile	…
budget.c	…
commit.c	…
compress.c	…
debug.c	UBIFS: rename random32() to prandom_u32()	12 years ago
debug.h	…
dir.c	new helper: file_inode(file)	12 years ago
file.c	Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs	12 years ago
find.c	…
gc.c	…
io.c	…
ioctl.c	new helper: file_inode(file)	12 years ago
journal.c	…
key.h	…
log.c	…
lprops.c	…
lpt.c	…
lpt_commit.c	UBIFS: rename random32() to prandom_u32()	12 years ago
master.c	…
misc.h	…
orphan.c	UBIFS: fix double free of ubifs_orphan objects	12 years ago
recovery.c	…
replay.c	…
sb.c	…
scan.c	…
shrinker.c	…
super.c	fs: Limit sys_mount to only request filesystem modules.	12 years ago
tnc.c	…
tnc_commit.c	UBIFS: rename random32() to prandom_u32()	12 years ago
tnc_misc.c	…
ubifs-media.h	…
ubifs.h	UBIFS: fix double free of ubifs_orphan objects	12 years ago
xattr.c	…