sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5e8f3f703ae4e4af65e2695e486b3cd198328863 · < 7f64cb5b4d8c872296eda0fdce3bcf099eec7aa7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start
In sctp_listen_start() invoked by sctp_inet_listen(), it should set the sk_state back to CLOSED if sctp_autobind() fails due to whatever reason.
Otherwise, next time when calling sctp_inet_listen(), if sctp_sk(sk)->reuse is already set via setsockopt(SCTP_REUSE_PORT), sctp_sk(sk)->bind_hash will be dereferenced as sk_state is LISTENING, which causes a crash as bind_hash is NULL.
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:sctp_inet_listen+0x7f0/0xa20 net/sctp/socket.c:8617 Call Trace: <TASK> __sys_listen_socket net/socket.c:1883 [inline] __sys_listen+0x1b7/0x230 net/socket.c:1894 __do_sys_listen net/socket.c:1902 [inline]
From the CVE record · Linux
The Linux kernel's SCTP listen handling can leave a socket in the LISTENING state when autobind fails. A subsequent local listen call can cause a null-pointer dereference and crash if SCTP_REUSE_PORT has been set. The input does not specify an authentication requirement.
Engineers running Linux kernels with SCTP support should check their kernel versions; affected versions are not specified.