CVE-2026-72242
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk46th percentile - higher than 46% of all known CVEs
Summary
In the Linux kernel SELinux module, selinux_sctp_bind_connect() dereferenced sk->sk_socket, which could cause issues when the hook was invoked from the ASCONF softirq path. The fix refactors the code to use struct sock * directly and avoid sk_socket dereference.
Risk Assessment
Dereferencing sk_socket in softirq context could lead to system crashes or incorrect SCTP behavior, potentially affecting network service stability.
Recommendation
It is recommended to update the Linux kernel to a version containing the fix and test SCTP functionality in production.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() selinux_sctp_bind_connect() dereferences sk->sk_socket to pass a struct socket * to selinux_socket_bind() and selinux_socket_connect_helper(). However, when the hook is invoked from the ASCONF softirq path (sctp_process_asconf), there is no file reference guaranteeing that sk->sk_socket is non-NULL. The setsockopt callers (bindx, connectx, set_primary, sendmsg connect) hold a file reference and are not affected. Both selinux_socket_bind() and selinux_socket_connect_helper() immediately resolve sock->sk, never using the struct socket * for anything else. Refactor the inner logic into helpers that take a struct sock * directly so that selinux_sctp_bind_connect() never needs to touch sk->sk_socket at all.