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… (CVE-2026-80984)
A vulnerability in the Linux kernel's SMC-D (Shared Memory Communications - Datagram) teardown path could cause a NULL pointer dereference when closing a socket. This occurs because the send buffer pointer may be unset and dereferenced during socket closure, leading to a fault. The issue arises from smc_close_stream_wait() calling smc_tx_prepared_sends() inside a condition evaluated without the socket lock, while the send buffer descriptor can be cleared concurrently. The vulnerability has been resolved by sampling the pointer once and handling the unset state safely.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel involves the net/smc subsystem where smc_close_stream_wait() calls smc_tx_prepared_sends() inside a sk_wait_event() condition that is evaluated once with the socket lock released. Meanwhile, smcd_buf_detach() clears the send buffer descriptor (conn->sndbuf_desc) under lock_sock() in smc_conn_kill(). This race condition can cause the helper function to dereference a NULL pointer during socket closure, resulting in a fault. The fix involves sampling the send buffer pointer once and reporting no prepared sends if it is unset, also bounding the ioctl accordingly. The receive tasklet dereferences the field directly but is not affected due to timing constraints.
Potential Impact
The vulnerability can cause a NULL pointer dereference leading to a fault during socket closure in the SMC-D subsystem of the Linux kernel. This could result in a denial of service by crashing the affected process or kernel thread handling the socket close operation. There is no indication of code execution or privilege escalation from the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The description indicates the vulnerability has been resolved, implying a fix is available. Users should apply the official Linux kernel updates that address this issue once released.
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… (CVE-2026-80984)
Description
A vulnerability in the Linux kernel's SMC-D (Shared Memory Communications - Datagram) teardown path could cause a NULL pointer dereference when closing a socket. This occurs because the send buffer pointer may be unset and dereferenced during socket closure, leading to a fault. The issue arises from smc_close_stream_wait() calling smc_tx_prepared_sends() inside a condition evaluated without the socket lock, while the send buffer descriptor can be cleared concurrently. The vulnerability has been resolved by sampling the pointer once and handling the unset state safely.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel involves the net/smc subsystem where smc_close_stream_wait() calls smc_tx_prepared_sends() inside a sk_wait_event() condition that is evaluated once with the socket lock released. Meanwhile, smcd_buf_detach() clears the send buffer descriptor (conn->sndbuf_desc) under lock_sock() in smc_conn_kill(). This race condition can cause the helper function to dereference a NULL pointer during socket closure, resulting in a fault. The fix involves sampling the send buffer pointer once and reporting no prepared sends if it is unset, also bounding the ioctl accordingly. The receive tasklet dereferences the field directly but is not affected due to timing constraints.
Potential Impact
The vulnerability can cause a NULL pointer dereference leading to a fault during socket closure in the SMC-D subsystem of the Linux kernel. This could result in a denial of service by crashing the affected process or kernel thread handling the socket close operation. There is no indication of code execution or privilege escalation from the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The description indicates the vulnerability has been resolved, implying a fix is available. Users should apply the official Linux kernel updates that address this issue once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-r783-4vmj-f363
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-80984"]
Threat ID: 6aa4a02955bf5e2cf5a86b26
Added to database: 09/12/2026, 00:43:21 UTC
Last enriched: 09/12/2026, 01:21:05 UTC
Last updated: 09/12/2026, 01:21:05 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.