diff options
| author | Tuong Lien <tuong.t.lien@dektech.com.au> | 2020-06-11 12:08:08 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-06-11 21:48:08 +0200 |
| commit | 9798278260e8f61d04415342544a8f701bc5ace7 (patch) | |
| tree | d431712690dc3493cf9d717a25c0c94ce7463993 /net/rxrpc/call_event.c | |
| parent | tipc: fix kernel WARNING in tipc_msg_append() (diff) | |
| download | linux-9798278260e8f61d04415342544a8f701bc5ace7.tar.xz linux-9798278260e8f61d04415342544a8f701bc5ace7.zip | |
tipc: fix NULL pointer dereference in tipc_disc_rcv()
When a bearer is enabled, we create a 'tipc_discoverer' object to store
the bearer related data along with a timer and a preformatted discovery
message buffer for later probing... However, this is only carried after
the bearer was set 'up', that left a race condition resulting in kernel
panic.
It occurs when a discovery message from a peer node is received and
processed in bottom half (since the bearer is 'up' already) just before
the discoverer object is created but is now accessed in order to update
the preformatted buffer (with a new trial address, ...) so leads to the
NULL pointer dereference.
We solve the problem by simply moving the bearer 'up' setting to later,
so make sure everything is ready prior to any message receiving.
Acked-by: Jon Maloy <jmaloy@redhat.com>
Signed-off-by: Tuong Lien <tuong.t.lien@dektech.com.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rxrpc/call_event.c')
0 files changed, 0 insertions, 0 deletions