CVE-2026-90065net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected d25a92ccae6bed02327b63d138e12e7806830f78 – < 2f4ece7fed6d915ec64b7735962c0d84d6261032
- affected d25a92ccae6bed02327b63d138e12e7806830f78 – < 84180988a455fd8e147c6b35c8df65d8b8cc76c2
- affected d25a92ccae6bed02327b63d138e12e7806830f78 – < 94a913cd521c0f0408820bcdbd80dadf076d97b5
- affected d25a92ccae6bed02327b63d138e12e7806830f78 – < cec261b0b4c5c0b044165303198d10ffcdf3414c
- affected 6.11
- unaffected < 6.11
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/2f4ece7fed6d915ec64b7735962c0d84d6261032 (opens in a new tab)
- https://git.kernel.org/stable/c/84180988a455fd8e147c6b35c8df65d8b8cc76c2 (opens in a new tab)
- https://git.kernel.org/stable/c/94a913cd521c0f0408820bcdbd80dadf076d97b5 (opens in a new tab)
- https://git.kernel.org/stable/c/cec261b0b4c5c0b044165303198d10ffcdf3414c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81926 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90065)Record last updated .