From: Eric Dumazet <hidden> Date: 2017-08-30 16:29:34
From: Eric Dumazet <redacted>
syzkaller had no problem to trigger a deadlock, attaching a KCM socket
to another one (or itself). (original syzkaller report was a very
confusing lockdep splat during a sendmsg())
It seems KCM claims to only support TCP, but no enforcement is done,
so we might need to add additional checks.
Fixes: ab7ac4eb9832 ("kcm: Kernel Connection Multiplexor module")
Signed-off-by: Eric Dumazet <redacted>
Reported-by: Dmitry Vyukov <dvyukov@google.com>
---
net/kcm/kcmsock.c | 4 ++++
1 file changed, 4 insertions(+)
From: Tom Herbert <hidden> Date: 2017-08-30 16:42:54
On Wed, Aug 30, 2017 at 9:29 AM, Eric Dumazet [off-list ref] wrote:
From: Eric Dumazet <redacted>
syzkaller had no problem to trigger a deadlock, attaching a KCM socket
to another one (or itself). (original syzkaller report was a very
confusing lockdep splat during a sendmsg())
It seems KCM claims to only support TCP, but no enforcement is done,
so we might need to add additional checks.
Fixes: ab7ac4eb9832 ("kcm: Kernel Connection Multiplexor module")
Signed-off-by: Eric Dumazet <redacted>
Reported-by: Dmitry Vyukov <dvyukov@google.com>
From: David Miller <davem@davemloft.net> Date: 2017-08-30 22:55:39
From: Eric Dumazet <redacted>
Date: Wed, 30 Aug 2017 09:29:31 -0700
From: Eric Dumazet <redacted>
syzkaller had no problem to trigger a deadlock, attaching a KCM socket
to another one (or itself). (original syzkaller report was a very
confusing lockdep splat during a sendmsg())
It seems KCM claims to only support TCP, but no enforcement is done,
so we might need to add additional checks.
Fixes: ab7ac4eb9832 ("kcm: Kernel Connection Multiplexor module")
Signed-off-by: Eric Dumazet <redacted>
Reported-by: Dmitry Vyukov <dvyukov@google.com>