CVE-2026-63976

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success

l2cap_ecred_reconf_rsp() returns early on success without clearing chan->ident. Every other L2CAP response handler (l2cap_ecred_conn_rsp, l2cap_le_connect_rsp, l2cap_config_rsp) clears chan->ident after a successful transaction to prevent the channel from matching subsequent responses with the recycled ident value.

A remote attacker that completed a reconfiguration as the peer can replay a failure response with the stale ident, causing the kernel to match and destroy the already-established channel via l2cap_chan_del(chan, ECONNRESET).

Clear chan->ident for all matching channels on success, and harden the failure path by using l2cap_chan_hold_unless_zero() consistent with other L2CAP handlers (l2cap_le_command_rej, __l2cap_get_chan_by_ident).

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59f5ecf6ad5c4db6ae81965a96156954a3b0d89a
generic

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b5b5f423b4fd23404a393bda8adba3cd6f74ef1
generic

Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00e1950716c6ed67d74777b2db286b0fa23b4be9

Vendor Advisories for CVE-2026-63976(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-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-oracle-7.0 (7.0.0-1008.8) @ 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 30× in last 7d / 156× 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 203 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-28 04:29 UTCVendor advisory
  7. 2026-08-28 04:29 UTCGHSA enrichment
  8. 2026-08-27 15:15 UTCEG score recompute
  9. 2026-08-27 15:15 UTCVendor advisory
  10. 2026-08-27 15:15 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 01:55 UTCEG score recompute
  13. 2026-08-27 01:55 UTCVendor advisory
  14. 2026-08-27 01:55 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 12:51 UTCVendor advisory
  17. 2026-08-26 12:51 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 10:11 UTCVendor advisory
  23. 2026-08-25 10:11 UTCGHSA enrichment
  24. 2026-08-24 21:05 UTCEG score recompute
  25. 2026-08-24 21:05 UTCVendor advisory
Show 75 more
  1. 2026-08-24 21:05 UTCGHSA enrichment
  2. 2026-08-24 08:00 UTCVendor advisory
  3. 2026-08-24 08:00 UTCGHSA enrichment
  4. 2026-08-23 18:53 UTCVendor advisory
  5. 2026-08-23 18:53 UTCGHSA enrichment
  6. 2026-08-23 05:48 UTCEG score recompute
  7. 2026-08-23 05:48 UTCVendor advisory
  8. 2026-08-23 05:47 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 16:42 UTCVendor advisory
  11. 2026-08-22 16:42 UTCGHSA enrichment
  12. 2026-08-22 03:31 UTCEG score recompute
  13. 2026-08-22 03:31 UTCVendor advisory
  14. 2026-08-22 03:31 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 14:26 UTCVendor advisory
  17. 2026-08-21 14:26 UTCGHSA enrichment
  18. 2026-08-21 01:20 UTCEG score recompute
  19. 2026-08-21 01:20 UTCVendor advisory
  20. 2026-08-21 01:20 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 12:14 UTCVendor advisory
  23. 2026-08-20 12:14 UTCGHSA enrichment
  24. 2026-08-19 23:09 UTCEG score recompute
  25. 2026-08-19 23:09 UTCVendor advisory
  26. 2026-08-19 23:09 UTCGHSA enrichment
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 09:09 UTCVendor advisory
  29. 2026-08-19 09:09 UTCGHSA enrichment
  30. 2026-08-18 19:50 UTCEG score recompute
  31. 2026-08-18 19:50 UTCVendor advisory
  32. 2026-08-18 19:50 UTCGHSA enrichment
  33. 2026-08-18 13:48 UTCEPSS rescore
  34. 2026-08-18 02:37 UTCEG score recompute
  35. 2026-08-18 02:37 UTCVendor advisory
  36. 2026-08-18 02:37 UTCGHSA enrichment
  37. 2026-08-17 13:47 UTCEPSS rescore
  38. 2026-08-17 13:31 UTCVendor advisory
  39. 2026-08-17 13:31 UTCGHSA enrichment
  40. 2026-08-17 00:26 UTCEG score recompute
  41. 2026-08-17 00:26 UTCVendor advisory
  42. 2026-08-17 00:26 UTCGHSA enrichment
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 11:20 UTCEG score recompute
  45. 2026-08-16 11:20 UTCVendor advisory
  46. 2026-08-16 11:20 UTCGHSA enrichment
  47. 2026-08-15 22:16 UTCVendor advisory
  48. 2026-08-15 22:16 UTCGHSA enrichment
  49. 2026-08-15 09:11 UTCEG score recompute
  50. 2026-08-15 09:11 UTCVendor advisory
  51. 2026-08-15 09:11 UTCGHSA enrichment
  52. 2026-08-15 01:30 UTCEPSS rescore
  53. 2026-08-14 20:05 UTCVendor advisory
  54. 2026-08-14 20:05 UTCGHSA enrichment
  55. 2026-08-14 07:00 UTCEG score recompute
  56. 2026-08-14 07:00 UTCVendor advisory
  57. 2026-08-14 07:00 UTCGHSA enrichment
  58. 2026-08-13 22:00 UTCEPSS rescore
  59. 2026-08-13 17:55 UTCVendor advisory
  60. 2026-08-13 17:55 UTCGHSA enrichment
  61. 2026-08-13 04:42 UTCVendor advisory
  62. 2026-08-13 04:42 UTCGHSA enrichment
  63. 2026-08-12 15:37 UTCEG score recompute
  64. 2026-08-12 15:37 UTCVendor advisory
  65. 2026-08-12 15:37 UTCGHSA enrichment
  66. 2026-08-12 13:51 UTCEPSS rescore
  67. 2026-08-12 02:31 UTCEG score recompute
  68. 2026-08-12 02:31 UTCVendor advisory
  69. 2026-08-12 02:31 UTCGHSA enrichment
  70. 2026-08-11 13:26 UTCVendor advisory
  71. 2026-08-11 13:26 UTCGHSA enrichment
  72. 2026-08-11 00:17 UTCEG score recompute
  73. 2026-08-11 00:17 UTCVendor advisory
  74. 2026-08-11 00:17 UTCGHSA enrichment
  75. 2026-08-11 00:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-63976?
CVE-2026-63976 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: clear chan->ident on ECRED reconfiguration success l2capecredreconf_rsp() returns early on success without clearing chan->ident. Every other L2CAP response handler (l2capecredconn_rsp, l2capleconnectrsp,…
When was CVE-2026-63976 disclosed?
CVE-2026-63976 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-63976 actively exploited?
CVE-2026-63976 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 62.3% of all scored CVEs.
What is the CVSS score of CVE-2026-63976?
CVE-2026-63976 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63976?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63976, 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-63976

Explore →

Is Your Infrastructure Affected by CVE-2026-63976?

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

Start Free Scan →Browse All CVEs