CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns()
In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix socket refcount leak in smcswitchconns()
smcswitchconns() takes a reference on the SMC socket before dropping lgr->connslock, so the connection stays alive while the CDC slot is fetched:
sockhold(&smc->sk); readunlockbh(&lgr->connslock); / pre-fetch buffer outside of sendlock, might sleep / rc = smccdcgetfreeslot(conn, tolnk, &wrbuf, NULL, &pend); if (rc) goto errout;
The errout label only drops the wrtx link reference, so this early exit returns without the matching sockput(). The second error exit is not affected, because sockput() has already run by then.
A leaked skrefcnt means the smcsock is never destroyed. Its send and receive buffers stay allocated, and for a user socket the reference held on the network namespace is never released, so the netns can no longer be torn down.
smccdcgetfreeslot() fails when the target link goes down or when the connection has been killed while the switch is in progress. Both are reachable during the link failover this function implements, so the leak is triggered by the same hardware events that make smcswitchconns() run in the first place.
Restructure so there is a single sockput() covering both outcomes, instead of adding a second one to the error path.
Affected Software
Event History
Frequently Asked Questions
Which systems are most likely to encounter this issue?
Systems using SMC connections that perform link failover are affected when a target link goes down or a connection is killed while a switch is in progress. These are the same hardware-failure conditions that cause the connection-switching path to run.
What is the practical impact of a triggered leak?
The affected SMC socket is never destroyed, leaving its send and receive buffers allocated. For user sockets, the associated network-namespace reference is also retained, preventing that network namespace from being torn down.
How can operators recognize that the issue has occurred?
A persistent SMC socket reference count and unreleased socket buffers after a failed connection switch indicate the leak. An inability to tear down a network namespace that has user SMC sockets is another observable consequence.