Answer in brief
CVE-2026-63971 records a Unknown severity vulnerability in sctp: fix race between sctp_wait_for_connect and peeloff. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63971 records a Unknown severity vulnerability in sctp: fix race between sctp_wait_for_connect and peeloff. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=668c9beb9020d5834ee9e43c208190a07d2b1928 <0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <bcfeac79af740735ace44008b4a11b8e5add20f5 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <8e9b56051d24540cfbf39194618708c4a7633549 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <634a9af8a26a84d8b0d7b3b643204b344b42d9fb || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <7d2038d4b80166f7bead8d07eba3b97405816c21 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <68667ee4c7dadf7f63167234e2a1af09b3f7874e || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <6140cfa721451fa6e18e134e709703c2bf34d0fb || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <f14fe6395a8b3d961a61e138ad7b36ba3626dd4e | 0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d, bcfeac79af740735ace44008b4a11b8e5add20f5, 8e9b56051d24540cfbf39194618708c4a7633549, 634a9af8a26a84d8b0d7b3b643204b344b42d9fb, 7d2038d4b80166f7bead8d07eba3b97405816c21, 68667ee4c7dadf7f63167234e2a1af09b3f7874e, 6140cfa721451fa6e18e134e709703c2bf34d0fb, f14fe6395a8b3d961a61e138ad7b36ba3626dd4e |
| Linux/Linuxgeneric | 4.16 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=668c9beb9020d5834ee9e43c208190a07d2b1928 <0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <bcfeac79af740735ace44008b4a11b8e5add20f5 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <8e9b56051d24540cfbf39194618708c4a7633549 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <634a9af8a26a84d8b0d7b3b643204b344b42d9fb || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <7d2038d4b80166f7bead8d07eba3b97405816c21 || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <68667ee4c7dadf7f63167234e2a1af09b3f7874e || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <6140cfa721451fa6e18e134e709703c2bf34d0fb || >=668c9beb9020d5834ee9e43c208190a07d2b1928 <f14fe6395a8b3d961a61e138ad7b36ba3626dd4e | 0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d, bcfeac79af740735ace44008b4a11b8e5add20f5, 8e9b56051d24540cfbf39194618708c4a7633549, 634a9af8a26a84d8b0d7b3b643204b344b42d9fb, 7d2038d4b80166f7bead8d07eba3b97405816c21, 68667ee4c7dadf7f63167234e2a1af09b3f7874e, 6140cfa721451fa6e18e134e709703c2bf34d0fb, f14fe6395a8b3d961a61e138ad7b36ba3626dd4e |
| Linux/Linuxgeneric | 4.16 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.