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 — 4 sources updated 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
6%
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(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 171× 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 224 total refreshes for this CVE.

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

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