CVE-2026-63971
Received Received - Intake

Race Condition in Linux Kernel SCTP Socket Handling

Publication date: 2026-07-19

Last updated on: 2026-07-19

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: sctp: fix race between sctp_wait_for_connect and peeloff sctp_wait_for_connect() drops and re-acquires the socket lock while waiting for the association to reach ESTABLISHED state. During this window, another thread can peeloff the association to a new socket via getsockopt(SCTP_SOCKOPT_PEELOFF), changing asoc->base.sk. After re-acquiring the old socket lock, sctp_wait_for_connect() returns success without noticing the migration — the caller then accesses the association under the wrong lock in sctp_datamsg_from_user(). Add the same sk != asoc->base.sk check that sctp_wait_for_sndbuf() already has, returning an error if the association was migrated while we slept.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-19
Last Modified
2026-07-19
Generated
2026-07-20
AI Q&A
2026-07-19
EPSS Evaluated
N/A
NVD
CVE-2026-63971
EUVD
EUVD-2026-45744

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a race condition between two operations: sctp_wait_for_connect and peeloff. sctp_wait_for_connect drops and re-acquires the socket lock while waiting for an association to reach the ESTABLISHED state. During this window, another thread can peel off the association to a new socket using getsockopt(SCTP_SOCKOPT_PEELOFF), changing the association's socket pointer. After re-acquiring the lock, sctp_wait_for_connect returns success without detecting this change, leading to incorrect access to the association under the wrong lock.

Detection Guidance

This vulnerability is specific to the Linux kernel's SCTP implementation and may not have direct detection commands. Monitor kernel logs for SCTP-related errors or crashes. Check for unexpected socket behavior or association migrations. Use tools like 'ss -tulnp' or 'netstat -tulnp' to inspect SCTP sockets.

Impact Analysis

This vulnerability could allow an attacker to manipulate the association migration process, potentially causing the kernel to access memory incorrectly. This might lead to system crashes, data corruption, or unauthorized access to sensitive information. Systems using SCTP (Stream Control Transmission Protocol) for network communication are primarily affected.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a race condition in the Linux kernel's SCTP implementation that could lead to incorrect socket state handling, but no evidence suggests it impacts data protection, privacy, or security controls required by these regulations.

Mitigation Strategies

Update the Linux kernel to the latest stable version that includes the fix for this vulnerability. If immediate patching is not possible, consider disabling SCTP if not required by your system. Monitor vendor advisories for kernel updates.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63971. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart