CVE-2026-90065net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from d25a92ccae6bed02327b63d138e12e7806830f78 before 2f4ece7fed6d915ec64b7735962c0d84d6261032; from d25a92ccae6bed02327b63d138e12e7806830f78 before 84180988a455fd8e147c6b35c8df65d8b8cc76c2; from d25a92ccae6bed02327b63d138e12e7806830f78 before 94a913cd521c0f0408820bcdbd80dadf076d97b5; from d25a92ccae6bed02327b63d138e12e7806830f78 before cec261b0b4c5c0b044165303198d10ffcdf3414c | CNA record |
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
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.