summaryrefslogtreecommitdiff
path: root/drivers/mfd/tps6507x.c
diff options
context:
space:
mode:
authorPeter Collingbourne <pcc@google.com>2021-08-26 12:46:01 -0700
committerDavid S. Miller <davem@davemloft.net>2021-08-27 09:40:25 +0100
commitd0efb16294d145d157432feda83877ae9d7cdf37 (patch)
tree8d1e461f01c5a30d866362a43c61b087e3c77081 /drivers/mfd/tps6507x.c
parent73367f05b25dbd064061aee780638564d15b01d1 (diff)
net: don't unconditionally copy_from_user a struct ifreq for socket ioctls
A common implementation of isatty(3) involves calling a ioctl passing a dummy struct argument and checking whether the syscall failed -- bionic and glibc use TCGETS (passing a struct termios), and musl uses TIOCGWINSZ (passing a struct winsize). If the FD is a socket, we will copy sizeof(struct ifreq) bytes of data from the argument and return -EFAULT if that fails. The result is that the isatty implementations may return a non-POSIX-compliant value in errno in the case where part of the dummy struct argument is inaccessible, as both struct termios and struct winsize are smaller than struct ifreq (at least on arm64). Although there is usually enough stack space following the argument on the stack that this did not present a practical problem up to now, with MTE stack instrumentation it's more likely for the copy to fail, as the memory following the struct may have a different tag. Fix the problem by adding an early check for whether the ioctl is a valid socket ioctl, and return -ENOTTY if it isn't. Fixes: 44c02a2c3dc5 ("dev_ioctl(): move copyin/copyout to callers") Link: https://linux-review.googlesource.com/id/I869da6cf6daabc3e4b7b82ac979683ba05e27d4d Signed-off-by: Peter Collingbourne <pcc@google.com> Cc: <stable@vger.kernel.org> # 4.19 Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/mfd/tps6507x.c')
0 files changed, 0 insertions, 0 deletions