CVE-2026-63971

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — Patch released this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f14fe6395a8b3d961a61e138ad7b36ba3626dd4e
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bcfeac79af740735ace44008b4a11b8e5add20f5
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e9b56051d24540cfbf39194618708c4a7633549
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d2038d4b80166f7bead8d07eba3b97405816c21
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68667ee4c7dadf7f63167234e2a1af09b3f7874e
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/634a9af8a26a84d8b0d7b3b643204b344b42d9fb
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6140cfa721451fa6e18e134e709703c2bf34d0fb
generic

sctp: fix race between sctp_wait_for_connect and peeloff - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e0d5bc76fd4267a71334fcc8f1a5fbcf997845d

Vendor Advisories for CVE-2026-63971(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-18ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-18ubuntu
redhatkernel-0:5.14.0-687.47.1.el9_82026-09-14redhat
redhatkernel-rt-0:4.18.0-553.162.1.rt7.503.el8_102026-09-10redhat
redhatkernel-0:4.18.0-553.162.1.el8_102026-09-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 100× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 275 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:22 UTCEG score recompute
  3. 2026-09-18 04:22 UTCVendor advisory
  4. 2026-09-18 04:22 UTCGHSA enrichment
  5. 2026-09-17 05:35 UTCEG score recompute
  6. 2026-09-17 05:35 UTCVendor advisory
  7. 2026-09-17 05:35 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 13:00 UTCEG score recompute
  10. 2026-09-16 13:00 UTCVendor advisory
  11. 2026-09-16 13:00 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-14 05:00 UTCVendor advisory
  14. 2026-09-14 05:00 UTCGHSA enrichment
  15. 2026-09-13 18:03 UTCEG score recompute
  16. 2026-09-13 18:03 UTCVendor advisory
  17. 2026-09-13 18:02 UTCGHSA enrichment
  18. 2026-09-13 07:03 UTCVendor advisory
  19. 2026-09-13 07:03 UTCGHSA enrichment
  20. 2026-09-12 19:48 UTCEG score recompute
  21. 2026-09-12 19:48 UTCVendor advisory
  22. 2026-09-12 19:48 UTCGHSA enrichment
  23. 2026-09-12 07:17 UTCVendor advisory
  24. 2026-09-12 07:17 UTCGHSA enrichment
  25. 2026-09-11 19:38 UTCEG score recompute
Show 75 more
  1. 2026-09-11 19:38 UTCVendor advisory
  2. 2026-09-11 19:38 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 23:28 UTCEG score recompute
  7. 2026-09-07 23:28 UTCVendor advisory
  8. 2026-09-07 23:28 UTCGHSA enrichment
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 12:58 UTCVendor advisory
  12. 2026-09-06 12:58 UTCGHSA enrichment
  13. 2026-09-05 20:05 UTCEG score recompute
  14. 2026-09-05 20:05 UTCVendor advisory
  15. 2026-09-05 20:05 UTCGHSA enrichment
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 05:07 UTCEPSS rescore
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-31 02:39 UTCEG score recompute
  22. 2026-08-31 02:39 UTCVendor advisory
  23. 2026-08-31 02:39 UTCGHSA enrichment
  24. 2026-08-30 19:17 UTCEPSS rescore
  25. 2026-08-30 15:39 UTCVendor advisory
  26. 2026-08-30 15:39 UTCGHSA enrichment
  27. 2026-08-30 02:54 UTCEG score recompute
  28. 2026-08-30 02:54 UTCVendor advisory
  29. 2026-08-30 02:54 UTCGHSA enrichment
  30. 2026-08-30 01:22 UTCEPSS rescore
  31. 2026-08-28 21:42 UTCEPSS rescore
  32. 2026-08-27 22:50 UTCEG score recompute
  33. 2026-08-27 22:50 UTCVendor advisory
  34. 2026-08-27 22:50 UTCGHSA enrichment
  35. 2026-08-27 14:25 UTCEPSS rescore
  36. 2026-08-27 11:52 UTCVendor advisory
  37. 2026-08-27 11:52 UTCGHSA enrichment
  38. 2026-08-26 22:43 UTCEG score recompute
  39. 2026-08-26 22:43 UTCVendor advisory
  40. 2026-08-26 22:43 UTCGHSA enrichment
  41. 2026-08-26 14:46 UTCEPSS rescore
  42. 2026-08-26 11:42 UTCVendor advisory
  43. 2026-08-26 11:42 UTCGHSA enrichment
  44. 2026-08-25 23:45 UTCEG score recompute
  45. 2026-08-25 23:45 UTCVendor advisory
  46. 2026-08-25 23:45 UTCGHSA enrichment
  47. 2026-08-25 13:49 UTCEPSS rescore
  48. 2026-08-25 12:37 UTCVendor advisory
  49. 2026-08-25 12:37 UTCGHSA enrichment
  50. 2026-08-25 01:39 UTCVendor advisory
  51. 2026-08-25 01:39 UTCGHSA enrichment
  52. 2026-08-24 14:42 UTCEG score recompute
  53. 2026-08-24 14:42 UTCVendor advisory
  54. 2026-08-24 14:42 UTCGHSA enrichment
  55. 2026-08-24 03:44 UTCVendor advisory
  56. 2026-08-24 03:44 UTCGHSA enrichment
  57. 2026-08-23 14:54 UTCVendor advisory
  58. 2026-08-23 14:54 UTCGHSA enrichment
  59. 2026-08-23 03:57 UTCEG score recompute
  60. 2026-08-23 03:57 UTCVendor advisory
  61. 2026-08-23 03:57 UTCGHSA enrichment
  62. 2026-08-23 00:19 UTCEPSS rescore
  63. 2026-08-22 16:59 UTCVendor advisory
  64. 2026-08-22 16:59 UTCGHSA enrichment
  65. 2026-08-22 06:00 UTCEG score recompute
  66. 2026-08-22 06:00 UTCVendor advisory
  67. 2026-08-22 06:00 UTCGHSA enrichment
  68. 2026-08-21 23:49 UTCEPSS rescore
  69. 2026-08-21 19:02 UTCGHSA enrichment
  70. 2026-08-21 08:02 UTCEG score recompute
  71. 2026-08-21 08:02 UTCVendor advisory
  72. 2026-08-21 08:02 UTCGHSA enrichment
  73. 2026-08-20 22:55 UTCEPSS rescore
  74. 2026-08-20 21:04 UTCVendor advisory
  75. 2026-08-20 21:04 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-63971?
CVE-2026-63971 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: sctp: fix race between sctpwaitfor_connect and peeloff sctpwaitfor_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…
When was CVE-2026-63971 disclosed?
CVE-2026-63971 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63971 actively exploited?
CVE-2026-63971 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63971?
CVE-2026-63971 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63971?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63971, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63971

Explore →

Is Your Infrastructure Affected by CVE-2026-63971?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs