diff options
author | Jan Harkes <jaharkes@cs.cmu.edu> | 2015-09-09 15:38:01 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-09-10 13:29:01 -0700 |
commit | 3725e9dd5bef376ab87d41e40c437a6b2a20eb59 (patch) | |
tree | 64bb811449dd09f596b2a2b6c5050a72087fe2ec /fs/hfs/bnode.c | |
parent | c5595fa2f1ce3c1a74dbd2ddc949257e80d81dc0 (diff) | |
download | linux-stable-3725e9dd5bef376ab87d41e40c437a6b2a20eb59.tar.gz linux-stable-3725e9dd5bef376ab87d41e40c437a6b2a20eb59.tar.bz2 linux-stable-3725e9dd5bef376ab87d41e40c437a6b2a20eb59.zip |
fs/coda: fix readlink buffer overflow
Dan Carpenter discovered a buffer overflow in the Coda file system
readlink code. A userspace file system daemon can return a 4096 byte
result which then triggers a one byte write past the allocated readlink
result buffer.
This does not trigger with an unmodified Coda implementation because Coda
has a 1024 byte limit for symbolic links, however other userspace file
systems using the Coda kernel module could be affected.
Although this is an obvious overflow, I don't think this has to be handled
as too sensitive from a security perspective because the overflow is on
the Coda userspace daemon side which already needs root to open Coda's
kernel device and to mount the file system before we get to the point that
links can be read.
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Jan Harkes <jaharkes@cs.cmu.edu>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/hfs/bnode.c')
0 files changed, 0 insertions, 0 deletions