Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80984net/smc: do not dereference an unset send buffer on the SMC-D teardown path

Description

In the Linux kernel, the following vulnerability has been resolved: net/smc: do not dereference an unset send buffer on the SMC-D teardown path smc_close_stream_wait() calls smc_tx_prepared_sends() from inside its sk_wait_event() condition, and sk_wait_event() evaluates that condition once with the socket lock released. smcd_buf_detach() clears conn->sndbuf_desc from smc_conn_kill() under lock_sock(), so a link group terminating while a socket waits there leaves the helper dereferencing NULL, faulting out of close(). SIOCOUTQ reads the field by hand, and smc_close_cancel_work() drops the lock across two cancel_*_sync() calls. Sample the pointer once in the helper, report nothing prepared while it is unset, and bound the ioctl the same way. The receive tasklet dereferences the field directly in smc_cdc_msg_recv_action(), not through this helper; 1/2 is what keeps it from running that late.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 21f6f41e82e59740e26e06e77bdf58dc7f6f08dd – < ab26e12dd5d2f43d939fcf456933a816e81d2e51
    • affected ae2be35cbed2c8385e890147ea321a3fcc3ca5fa – < e3fcff8d22a6c9540748846cd800443a643553a6
    • affected ae2be35cbed2c8385e890147ea321a3fcc3ca5fa – < f950e1b1f0aad334f9a9ee552c4dd5b794ebdd45
    • affected ae2be35cbed2c8385e890147ea321a3fcc3ca5fa – < f517cf02033801a28f98d86ca613a3533cf066b3
    • affected ae2be35cbed2c8385e890147ea321a3fcc3ca5fa – < b395dd319cea422239cb45b998fb38d7e373af87
    • affected 6.6.66 – < 6.6.157
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80984 badge
[![CVE-2026-80984](https://cveledger.app/badge/CVE-2026-80984.svg)](https://cveledger.app/cve/CVE-2026-80984)

Record last updated .