aboutsummaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2016-12-16 13:42:06 -0500
committerAndreas Blaesius <skate4life@gmx.de>2017-03-17 11:02:29 +0100
commit1f19ffb5170347ac667f6cc3450b30fcd72b054c (patch)
tree22c8c387ce5718e6c4661e0ab070048a49049dbb /block
parent22837db7f47b8147a31f06c4c064d4268798a8bc (diff)
downloadkernel_samsung_espresso10-1f19ffb5170347ac667f6cc3450b30fcd72b054c.zip
kernel_samsung_espresso10-1f19ffb5170347ac667f6cc3450b30fcd72b054c.tar.gz
kernel_samsung_espresso10-1f19ffb5170347ac667f6cc3450b30fcd72b054c.tar.bz2
sg_write()/bsg_write() is not fit to be called under KERNEL_DS
Both damn things interpret userland pointers embedded into the payload; worse, they are actually traversing those. Leaving aside the bad API design, this is very much _not_ safe to call with KERNEL_DS. Bail out early if that happens. Change-Id: I9fe7a5855db598eaa515007603b7e327aee74305 Cc: stable@vger.kernel.org Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'block')
-rw-r--r--block/bsg.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/block/bsg.c b/block/bsg.c
index 792ead6..73e5eb4 100644
--- a/block/bsg.c
+++ b/block/bsg.c
@@ -675,6 +675,9 @@ bsg_write(struct file *file, const char __user *buf, size_t count, loff_t *ppos)
dprintk("%s: write %Zd bytes\n", bd->name, count);
+ if (unlikely(segment_eq(get_fs(), KERNEL_DS)))
+ return -EINVAL;
+
bsg_set_block(bd, file);
bytes_written = 0;