summaryrefslogtreecommitdiff
path: root/net/lapb/lapb_timer.c
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2016-02-13 05:34:52 +0300
committerBen Hutchings <ben@decadent.org.uk>2016-02-27 17:28:49 +0300
commitfeae3ca2e5e1a8f44aa6290255d3d9709985d0b2 (patch)
treea2a2372876b0407218ff669911080eea32e7cf6f /net/lapb/lapb_timer.c
parent4249217f43bc2d1f0ba71895a566d28d8d097d52 (diff)
downloadlinux-feae3ca2e5e1a8f44aa6290255d3d9709985d0b2.tar.xz
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. References: https://rhn.redhat.com/errata/RHSA-2016-0103.html Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions