SECUFOCUSNOW
Home›CVE index›CVE-2026-63971
Review reviewHigh

CVE-2026-63971

Linux

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...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux
Affected versions
>= 668c9beb9020d5834ee9e43c208190a07d2b1928 < 0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < bcfeac79af740735ace44008b4a11b8e5add20f5, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < 8e9b56051d24540cfbf39194618708c4a7633549, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < 634a9af8a26a84d8b0d7b3b643204b344b42d9fb, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < 7d2038d4b80166f7bead8d07eba3b97405816c21, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < 68667ee4c7dadf7f63167234e2a1af09b3f7874e, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < 6140cfa721451fa6e18e134e709703c2bf34d0fb, >= 668c9beb9020d5834ee9e43c208190a07d2b1928 < f14fe6395a8b3d961a61e138ad7b36ba3626dd4e, >= 4.16
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available