Browse files

pipe: Fix buffer offset after partially failed read

Quoting the RHEL advisory:

> It was found that the fix for CVE-2015-1805 incorrectly kept buffer
> offset and buffer length in sync on a failed atomic read, potentially
> resulting in a pipe buffer state corruption. A local, unprivileged user
> could use this flaw to crash the system or leak kernel memory to user
> space. (CVE-2016-0774, Moderate)

The same flawed fix was applied to stable branches from 2.6.32.y to
3.14.y inclusive, and I was able to reproduce the issue on 3.2.y.
We need to give pipe_iov_copy_to_user() a separate offset variable
and only update the buffer offset if it succeeds.

Change-Id: I988802f38acf40c7671fa0978880928b02d29b56
Signed-off-by: Ben Hutchings <>
(cherry picked from commit feae3ca2e5e1a8f44aa6290255d3d9709985d0b2)
  • Loading branch information...
bwhacks authored and andi34 committed Feb 13, 2016
1 parent 923ab46 commit 4dc98567e1449b4e7fe6b3d01eecfcb1f7e9ae21
Showing with 4 additions and 1 deletion.
  1. +4 −1 fs/pipe.c
@@ -389,6 +389,7 @@ pipe_read(struct kiocb *iocb, const struct iovec *_iov,
void *addr;
size_t chars = buf->len, remaining;
int error, atomic;
int offset;
if (chars > total_len)
chars = total_len;
@@ -402,9 +403,10 @@ pipe_read(struct kiocb *iocb, const struct iovec *_iov,
atomic = !iov_fault_in_pages_write(iov, chars);
remaining = chars;
offset = buf->offset;
addr = ops->map(pipe, buf, atomic);
error = pipe_iov_copy_to_user(iov, addr, &buf->offset,
error = pipe_iov_copy_to_user(iov, addr, &offset,
&remaining, atomic);
ops->unmap(pipe, buf, addr);
if (unlikely(error)) {
@@ -420,6 +422,7 @@ pipe_read(struct kiocb *iocb, const struct iovec *_iov,
ret += chars;
buf->offset += chars;
buf->len -= chars;
/* Was it a packet buffer? Clean up and exit */

0 comments on commit 4dc9856

Please sign in to comment.