Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80983: net/smc: fix socket refcount leak in smc_switch_conns()

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 09d7a9e162ee1a269878c126aee3d7eff43e4130, 5.10.273, 5.15; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 09d7a9e162ee1a269878c126aee3d7eff43e4130, 5.10.273, 5.15; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80983

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 0d9ddf515cde793841f738490037560fd6559c63, 5.15affected
    • 99f19566b1c4d3dc4d934ee2ef43faadebb56d70 and later · before 8cb289eb764ff18000a33ddbc287d676d8597eeaaffected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before a3378466704e0bbe93aef9769552dca7673a7eb6affected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before e20227019d9da73f8fdf16f0951c2e188c84933faffected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before 09d7a9e162ee1a269878c126aee3d7eff43e4130affected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before 84dea0585f6b538ae895a8b1d025f4897737f3b1affected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before d89dc1bd8845c669a700eee58c64ebd3cc1b6d2daffected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before d9a879ac25958bdaecb669ce70e58f8e2ff170deaffected · git
    • 95f7f3e7dc6bd2e735cb5de11734ea2222b1e05a and later · before 719296c4aa8213d4ac8002e77d5956d436bc98d0affected · git
    • 5.10.90 and later · before 5.10.273affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80981Sep 11, 2026 · net/smc: fix use-after-free of the LLC qentry in smc_llc_srv_add_link()
    39Monitor
  • ← EarlierCVE-2026-80982Sep 11, 2026 · net/smc: fix use-after-free in smc_rx_pipe_buf_release()
    31Monitor
  • Later →CVE-2026-80984Sep 11, 2026 · net/smc: do not dereference an unset send buffer on the SMC-D teardown path
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux09d7a9e162ee1a269878c126aee3d7eff43e4130Vendor (CNA)
Linux Linux5.10.273Vendor (CNA)
Linux Linux5.15Vendor (CNA)
Linux Linux719296c4aa8213d4ac8002e77d5956d436bc98d0Vendor (CNA)
Linux Linux84dea0585f6b538ae895a8b1d025f4897737f3b1Vendor (CNA)
Linux Linux8cb289eb764ff18000a33ddbc287d676d8597eeaVendor (CNA)
Linux Linuxa3378466704e0bbe93aef9769552dca7673a7eb6Vendor (CNA)
Linux Linuxd89dc1bd8845c669a700eee58c64ebd3cc1b6d2dVendor (CNA)
Linux Linuxd9a879ac25958bdaecb669ce70e58f8e2ff170deVendor (CNA)
Linux Linuxe20227019d9da73f8fdf16f0951c2e188c84933fVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records