Revision 9c1c2b35f1d94de8325344c2777d7ee67492db3b authored by Jeff Layton on 03 April 2019, 17:16:01 UTC, committed by Ilya Dryomov on 21 January 2020, 18:02:37 UTC
Currently, we just assume that it will stick around by virtue of the
submitter's reference, but later patches will allow the syscall to
return early and we can't rely on that reference at that point.

While I'm not aware of any reports of it, Xiubo pointed out that this
may fix a use-after-free.  If the wait for a reply times out or is
canceled via signal, and then the reply comes in after the syscall
returns, the client can end up trying to access r_parent without a
reference.

Take an extra reference to the inode when setting r_parent and release
it when releasing the request.

Cc: stable@vger.kernel.org
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
1 parent def9d27
History
File Mode Size
Makefile -rw-r--r-- 801 bytes
__clear_user.S -rw-r--r-- 1.8 KB
ashiftrt.S -rw-r--r-- 2.3 KB
ashldi3.c -rw-r--r-- 511 bytes
ashlsi3.S -rw-r--r-- 2.8 KB
ashrdi3.c -rw-r--r-- 535 bytes
ashrsi3.S -rw-r--r-- 2.8 KB
checksum.S -rw-r--r-- 7.1 KB
copy_page.S -rw-r--r-- 6.1 KB
delay.c -rw-r--r-- 1.1 KB
div64-generic.c -rw-r--r-- 319 bytes
div64.S -rw-r--r-- 586 bytes
io.c -rw-r--r-- 1.9 KB
libgcc.h -rw-r--r-- 423 bytes
lshrdi3.c -rw-r--r-- 513 bytes
lshrsi3.S -rw-r--r-- 2.8 KB
mcount.S -rw-r--r-- 5.2 KB
memchr.S -rw-r--r-- 412 bytes
memcpy-sh4.S -rw-r--r-- 15.3 KB
memcpy.S -rw-r--r-- 3.6 KB
memmove.S -rw-r--r-- 4.0 KB
memset-sh4.S -rw-r--r-- 1.6 KB
memset.S -rw-r--r-- 867 bytes
movmem.S -rw-r--r-- 4.2 KB
strlen.S -rw-r--r-- 827 bytes
udiv_qrnnd.S -rw-r--r-- 1.1 KB
udivsi3.S -rw-r--r-- 1015 bytes
udivsi3_i4i-Os.S -rw-r--r-- 2.3 KB
udivsi3_i4i.S -rw-r--r-- 8.9 KB

back to top