Re: KASAN: use-after-free Read in lock_sock_nested

2019-02-14 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:b3418f8bddf4 Add linux-next specific files for 20190214 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=14f6304740 kernel config: https://syzkaller.appspot.com/x/.config?x

Re: general protection fault in prepare_to_wait

2019-02-14 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:23e93c9b2cde Revert "gfs2: read journal in large chunks to.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14e94014c0 kernel config:

[PATCH AUTOSEL 4.4 16/20] ax25: fix possible use-after-free

2019-02-14 Thread Sasha Levin
From: Eric Dumazet [ Upstream commit 63530aba7826a0f8e129874df9c4d264f9db3f9e ] syzbot found that ax25 routes where not properly protected against concurrent use [1]. In this particular report the bug happened while copying ax25->digipeat. Fix this problem by making sure we call

[PATCH AUTOSEL 4.9 20/27] ax25: fix possible use-after-free

2019-02-14 Thread Sasha Levin
From: Eric Dumazet [ Upstream commit 63530aba7826a0f8e129874df9c4d264f9db3f9e ] syzbot found that ax25 routes where not properly protected against concurrent use [1]. In this particular report the bug happened while copying ax25->digipeat. Fix this problem by making sure we call

[PATCH AUTOSEL 4.14 32/40] ax25: fix possible use-after-free

2019-02-14 Thread Sasha Levin
From: Eric Dumazet [ Upstream commit 63530aba7826a0f8e129874df9c4d264f9db3f9e ] syzbot found that ax25 routes where not properly protected against concurrent use [1]. In this particular report the bug happened while copying ax25->digipeat. Fix this problem by making sure we call

[PATCH AUTOSEL 4.20 59/77] ax25: fix possible use-after-free

2019-02-14 Thread Sasha Levin
From: Eric Dumazet [ Upstream commit 63530aba7826a0f8e129874df9c4d264f9db3f9e ] syzbot found that ax25 routes where not properly protected against concurrent use [1]. In this particular report the bug happened while copying ax25->digipeat. Fix this problem by making sure we call