diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-01-05 16:26:00 -0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-02-03 17:04:24 +0100 |
commit | b392225467b8066538dfa200dc925c844b76880b (patch) | |
tree | 9f1c7c3de61ea5e272a37db92abfb2a02107227c /crypto/hash_info.c | |
parent | 49fe90b853dfb1087d0a734cd7f4af1aa00c8e53 (diff) |
loop: fix concurrent lo_open/lo_release
commit ae6650163c66a7eff1acd6eb8b0f752dcfa8eba5 upstream.
范龙飞 reports that KASAN can report a use-after-free in __lock_acquire.
The reason is due to insufficient serialization in lo_release(), which
will continue to use the loop device even after it has decremented the
lo_refcnt to zero.
In the meantime, another process can come in, open the loop device
again as it is being shut down. Confusion ensues.
Reported-by: 范龙飞 <long7573@126.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Cc: Ben Hutchings <ben.hutchings@codethink.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/hash_info.c')
0 files changed, 0 insertions, 0 deletions