• Jan Harkes's avatar
    coda: fix 'kernel memory exposure attempt' in fsync · 71d3850b
    Jan Harkes authored
    commit d337b66a4c52c7b04eec661d86c2ef6e168965a2 upstream.
    
    When an application called fsync on a file in Coda a small request with
    just the file identifier was allocated, but the declared length was set
    to the size of union of all possible upcall requests.
    
    This bug has been around for a very long time and is now caught by the
    extra checking in usercopy that was introduced in Linux-4.8.
    
    The exposure happens when the Coda cache manager process reads the fsync
    upcall request at which point it is killed. As a result there is nobody
    servicing any further upcalls, trapping any processes that try to access
    the mounted Coda filesystem.
    Signed-off-by: 's avatarJan Harkes <jaharkes@cs.cmu.edu>
    Signed-off-by: 's avatarAl Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
    71d3850b
Name
Last commit
Last update
..
Kconfig Loading commit data...
Makefile Loading commit data...
cache.c Loading commit data...
cnode.c Loading commit data...
coda_cache.h Loading commit data...
coda_fs_i.h Loading commit data...
coda_int.h Loading commit data...
coda_linux.c Loading commit data...
coda_linux.h Loading commit data...
dir.c Loading commit data...
file.c Loading commit data...
inode.c Loading commit data...
pioctl.c Loading commit data...
psdev.c Loading commit data...
symlink.c Loading commit data...
sysctl.c Loading commit data...
upcall.c Loading commit data...