Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure IPPROTO_SMC sockets create an internal TCP sock ("clcsock") from the proto->init hook. When socket creation fails after proto->init has run - e.g. a cgroup BPF program attached to BPF_CGROUP_INET_SOCK_CREATE denies the socket - sk_common_release() only invokes sk_prot->destroy if it is set, but neither smc_inet_prot nor smc_inet6_prot defines it, and smc_destruct() returns early unless sk_state is SMC_CLOSED. As a result, every failing socket(AF_INET, SOCK_STREAM, IPPROTO_SMC) call leaks one tcp_sock, so an unprivileged task able to attach a deny-all BPF_CGROUP_INET_SOCK_CREATE program to its own cgroup can grow kernel memory unboundedly. Add a .destroy hook to both protos that releases the clcsock via smc_clcsock_release(). smc_sk_init() hashes the sock into the smc hashinfo before the clcsock is created, and smc_diag dumps walk that hash dereferencing smc->clcsock without taking clcsock_release_lock, while sk_common_release() calls .destroy before .unhash. Unhash the sock before releasing the clcsock, as __smc_release() does, so a concurrent dump cannot observe the release; the second unhash in sk_common_release() is a no-op.
References
- https://git.kernel.org/stable/c/2f4ece7fed6d915ec64b7735962c0d84d6261032
- https://git.kernel.org/stable/c/84180988a455fd8e147c6b35c8df65d8b8cc76c2
- https://git.kernel.org/stable/c/94a913cd521c0f0408820bcdbd80dadf076d97b5
- https://git.kernel.org/stable/c/cec261b0b4c5c0b044165303198d10ffcdf3414c
FAQ
What is CVE-2026-90065?
CVE-2026-90065 is a documented vulnerability. In the Linux kernel, the following vulnerability has been resolved: net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure IPPROTO_SMC sockets create an internal TCP sock ("cl...
How severe is CVE-2026-90065?
CVSS scoring is not yet available for CVE-2026-90065. Check NVD for updates.
Is there a patch for CVE-2026-90065?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.