cbcvebase.
CVE-2022-50555
published 2025-10-07

CVE-2022-50555: In the Linux kernel, the following vulnerability has been resolved: tipc: fix a null-ptr-deref in tipc_topsrv_accept syzbot found a crash in…

PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
10.3th percentile
In the Linux kernel, the following vulnerability has been resolved: tipc: fix a null-ptr-deref in tipc_topsrv_accept syzbot found a crash in tipc_topsrv_accept: KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] Workqueue: tipc_rcv tipc_topsrv_accept RIP: 0010:kernel_accept+0x22d/0x350 net/socket.c:3487 Call Trace: tipc_topsrv_accept+0x197/0x280 net/tipc/topsrv.c:460 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 It was caused by srv->listener that might be set to null by tipc_topsrv_stop() in net .exit whereas it's still used in tipc_topsrv_accept() worker. srv->listener is protected by srv->idr_lock in tipc_topsrv_stop(), so add a check for srv->listener under srv->idr_lock in tipc_topsrv_accept() to avoid the null-ptr-deref. To ensure the lsock is not released during the tipc_topsrv_accept(), move sock_release() after tipc_topsrv_work_stop() where it's waiting until the tipc_topsrv_accept worker to be done. Note that sk_callback_lock is used to protect sk->sk_user_data instead of srv->listener, and it should check srv in tipc_topsrv_listener_data_ready() instead. This also ensures that no more tipc_topsrv_accept worker will be started after tipc_conn_close() is called in tipc_topsrv_stop() where it sets sk->sk_user_data to null.

Affected

19 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.0.7-1 (bookworm)linux 6.0.7-1 (bookworm)
linuxlinux——
linuxlinux>= 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 < ce69bdac2310152bb70845024d5d704c52aabfc3ce69bdac2310152bb70845024d5d704c52aabfc3
linuxlinux>= 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 < 24b129aed8730e48f47d852d58d76825ab6f407c24b129aed8730e48f47d852d58d76825ab6f407c
linuxlinux>= 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 < 32a3d4660b34ce49ac0162338ebe362098e2f5df32a3d4660b34ce49ac0162338ebe362098e2f5df
linuxlinux>= 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 < 7a939503fc32bff4ed60800b73ff7fbb4aea21427a939503fc32bff4ed60800b73ff7fbb4aea2142
linuxlinux>= 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 < cedb41664e27b2cae7e21487f1bee22dcd84037dcedb41664e27b2cae7e21487f1bee22dcd84037d
linuxlinux>= 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 < 82cb4e4612c633a9ce320e1773114875604a3cce82cb4e4612c633a9ce320e1773114875604a3cce
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel>= 0 < 5.10.158-15.10.158-1
linuxlinux_kernel>= 0 < 6.0.7-16.0.7-1
linuxlinux_kernel>= 0 < 6.0.7-16.0.7-1
linuxlinux_kernel>= 0 < 6.0.7-16.0.7-1
linuxlinux_kernel>= 4.17 < 4.19.2644.19.264
linuxlinux_kernel>= 4.20 < 5.4.2235.4.223
linuxlinux_kernel>= 5.11 < 5.15.775.15.77
linuxlinux_kernel>= 5.16 < 6.0.76.0.7
linuxlinux_kernel>= 5.5 < 5.10.1535.10.153

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.