Answer in brief
CVE-2026-80983 records a Unknown severity vulnerability in net/smc: fix socket refcount leak in smc_switch_conns(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <84dea0585f6b538ae895a8b1d025f4897737f3b1 || >=95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <d89dc1bd8845c669a700eee58c64ebd3cc1b6d2d || >=95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <d9a879ac25958bdaecb669ce70e58f8e2ff170de || >=95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <719296c4aa8213d4ac8002e77d5956d436bc98d0 || 99f19566b1c4d3dc4d934ee2ef43faadebb56d70 || 0d9ddf515cde793841f738490037560fd6559c63 || >=5.10.90 <5.11 || >=5.14.14 <5.15 | 84dea0585f6b538ae895a8b1d025f4897737f3b1, d89dc1bd8845c669a700eee58c64ebd3cc1b6d2d, d9a879ac25958bdaecb669ce70e58f8e2ff170de, 719296c4aa8213d4ac8002e77d5956d436bc98d0, 5.11, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix socket refcount leak in smc_switch_conns() smc_switch_conns() takes a reference on the SMC socket before dropping lgr->conns_lock, so the connection stays alive while the CDC slot is fetched: sock_hold(&smc->sk); read_unlock_bh(&lgr->conns_lock); /* pre-fetch buffer outside of send_lock, might sleep */ rc = smc_cdc_get_free_slot(conn, to_lnk, &wr_buf, NULL, &pend); if (rc) goto err_out; The err_out label only drops the wr_tx link reference, so this early exit returns without the matching sock_put(). The second error exit is not affected, because sock_put() has already run by then. A leaked sk_refcnt means the smc_sock 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. smc_cdc_get_free_slot() 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 smc_switch_conns() run in the first place. Restructure so there is a single sock_put() covering both outcomes, instead of adding a second one to the error path.
Quoted source text, attributed separately from HOL analysis.