CVE-2026-80983

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 14, 2026

Vendor Advisories for CVE-2026-80983(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 13× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 57 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 19:21 UTCEG score recompute
  5. 2026-10-11 16:37 UTCEG score recompute
  6. 2026-10-11 13:55 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-10 17:12 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-07 19:46 UTCVendor advisory
  13. 2026-10-07 19:46 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-04 20:26 UTCVendor advisory
  18. 2026-10-04 20:26 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-01 22:33 UTCVendor advisory
  22. 2026-10-01 22:33 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-29 01:06 UTCEG score recompute
Show 31 more
  1. 2026-09-29 01:06 UTCVendor advisory
  2. 2026-09-29 01:06 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  3. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-26 03:36 UTCVendor advisory
  7. 2026-09-26 03:36 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  8. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-23 05:55 UTCVendor advisory
  12. 2026-09-23 05:55 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  13. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-20 08:29 UTCVendor advisory
  17. 2026-09-20 08:29 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  18. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-17 11:01 UTCVendor advisory
  20. 2026-09-17 11:01 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  21. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-14 13:35 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  25. 2026-09-14 13:27 UTCNVD update
  26. 2026-09-14 12:32 UTCEG score recompute
  27. 2026-09-14 12:32 UTCGHSA enrichmentGHSA-6pmg-4m98-jhww
  28. 2026-09-14 12:24 UTCMITRE cvelistV5
  29. 2026-09-11 20:36 UTCNVD update
  30. 2026-09-11 19:53 UTCEG score recompute
  31. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80983?
CVE-2026-80983 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. 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->conns_lock, so the connection stays alive while the CDC slot is fetched: sock_hold(&smc->sk);…
When was the CVE record for CVE-2026-80983 published?
The CVE record for CVE-2026-80983 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-80983 actively exploited?
CVE-2026-80983 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80983?
A fix for CVE-2026-80983 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80983 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80983

Explore →

Is Your Infrastructure Affected by CVE-2026-80983?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.