diff options
author | Duoming Zhou <duoming@zju.edu.cn> | 2022-03-26 18:43:46 +0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2022-03-26 11:48:16 -0700 |
commit | 7781607938c8371d4c2b243527430241c62e39c2 (patch) | |
tree | 6dcb49a0273aa15819085ecd0e811821798e9a1f /net/tipc/socket.c | |
parent | 1521db37f0d42334a88e8ff28198a27d1ed5cd7b (diff) | |
download | linux-7781607938c8371d4c2b243527430241c62e39c2.tar.bz2 |
net/x25: Fix null-ptr-deref caused by x25_disconnect
When the link layer is terminating, x25->neighbour will be set to NULL
in x25_disconnect(). As a result, it could cause null-ptr-deref bugs in
x25_sendmsg(),x25_recvmsg() and x25_connect(). One of the bugs is
shown below.
(Thread 1) | (Thread 2)
x25_link_terminated() | x25_recvmsg()
x25_kill_by_neigh() | ...
x25_disconnect() | lock_sock(sk)
... | ...
x25->neighbour = NULL //(1) |
... | x25->neighbour->extended //(2)
The code sets NULL to x25->neighbour in position (1) and dereferences
x25->neighbour in position (2), which could cause null-ptr-deref bug.
This patch adds lock_sock() in x25_kill_by_neigh() in order to synchronize
with x25_sendmsg(), x25_recvmsg() and x25_connect(). What`s more, the
sock held by lock_sock() is not NULL, because it is extracted from x25_list
and uses x25_list_lock to synchronize.
Fixes: 4becb7ee5b3d ("net/x25: Fix x25_neigh refcnt leak when x25 disconnect")
Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
Reviewed-by: Lin Ma <linma@zju.edu.cn>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc/socket.c')
0 files changed, 0 insertions, 0 deletions