CVE-2026-80984

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

N/A
Published: September 11, 2026 at 07:42 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

21f6f41e82e59740e26e06e77bdf58dc7f6f08dd6.106.6.66ae2be35cbed2c8385e890147ea321a3fcc3ca5fa
Vendor states this is fixed in ab26e12dd5d2f43d939fcf456933a816e81d2e51 (fixed)
Vendor states this is fixed in b395dd319cea422239cb45b998fb38d7e373af87 (fixed)
Vendor states this is fixed in e3fcff8d22a6c9540748846cd800443a643553a6 (fixed)
Vendor states this is fixed in f517cf02033801a28f98d86ca613a3533cf066b3 (fixed)
Vendor states this is fixed in f950e1b1f0aad334f9a9ee552c4dd5b794ebdd45 (fixed)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card