![]() 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:
|
||
---|---|---|
.. | ||
kcmproc.c | ||
kcmsock.c | ||
Kconfig | ||
Makefile |