CVE-2026-80983

CVE CVE-2026-80983EUVD EUVD-2026-76306Published 2026-09-11T19:42:42.000ZLast changed 2026-09-14T11:59:26.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 5.15.221; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <a3378466704e0bbe93aef9769552dca7673a7eb6; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <09d7a9e162ee1a269878c126aee3d7eff43e4130; 5.15; 0d9ddf515cde793841f738490037560fd6559c63; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <d9a879ac25958bdaecb669ce70e58f8e2ff170de; patch: 6.6.157; patch: 6.18.50; 5.14.14 <5.15; patch: 6.1.188; patch: 7.3-rc1; 5.10.90 <5.11; patch: 7.2.4; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <719296c4aa8213d4ac8002e77d5956d436bc98d0; 99f19566b1c4d3dc4d934ee2ef43faadebb56d70; patch: 0; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <84dea0585f6b538ae895a8b1d025f4897737f3b1; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <e20227019d9da73f8fdf16f0951c2e188c84933f; patch: 6.12.109; 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a <d89dc1bd8845c669a700eee58c64ebd3cc1b6d2d

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.