CVE-2026-72242
CVE CVE-2026-72242EUVD EUVD-2026-59141Published 2026-08-15T05:54:30.000ZLast changed 2026-08-17T05:41:55.000ZCVSS 7.5
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d452930fd3b9031e59abfeddb2fa383f1403d61a <cc8bd47b35eca82393cbad08b1cc86f02e034439; patch: 0; patch: 7.2; patch: 6.18.40; d452930fd3b9031e59abfeddb2fa383f1403d61a <5d4d93f9bfbc997ffbb03cd6107e8f6979dbb9b4; patch: 6.6.148; d452930fd3b9031e59abfeddb2fa383f1403d61a <37d642b37ccdc31e1947c2ebc8dc38f03d4a0ceb; d452930fd3b9031e59abfeddb2fa383f1403d61a <56acfeb10019e200ab6787d01f8d7cbe0f01526f; patch: 7.1.5; d452930fd3b9031e59abfeddb2fa383f1403d61a <d61a80b17254be7230bc5544f8e62ddf21ab38e2; 4.17; patch: 6.12.97
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.