CVE-2026-31772

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync

hci_le_big_create_sync() uses DEFINE_FLEX to allocate a struct hci_cp_le_big_create_sync on the stack with room for 0x11 (17) BIS entries. However, conn->num_bis can hold up to HCI_MAX_ISO_BIS (31) entries — validated against ISO_MAX_NUM_BIS (0x1f) in the caller hci_conn_big_create_sync(). When conn->num_bis is between 18 and 31, the memcpy that copies conn->bis into cp->bis writes up to 14 bytes past the stack buffer, corrupting adjacent stack memory.

This is trivially reproducible: binding an ISO socket with bc_num_bis = ISO_MAX_NUM_BIS (31) and calling listen() will eventually trigger hci_le_big_create_sync() from the HCI command sync worker, causing a KASAN-detectable stack-out-of-bounds write:

BUG: KASAN: stack-out-of-bounds in hci_le_big_create_sync+0x256/0x3b0 Write of size 31 at addr ffffc90000487b48 by task kworker/u9:0/71

Fix this by changing the DEFINE_FLEX count from the incorrect 0x11 to HCI_MAX_ISO_BIS, which matches the maximum number of BIS entries that conn->bis can actually carry.

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
4%
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aba0aea354015794e8312dd7efe726967e58aefe

Vendor Advisories for CVE-2026-31772(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-687.17.1.el9_82026-06-22redhat
redhatkernel-0:6.12.0-211.26.1.el10_22026-06-20redhat
linuxKernel @ 6.12.81osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-31772?
CVE-2026-31772 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: fix stack buffer overflow in hcilebigcreate_sync hcilebigcreatesync() uses DEFINE_FLEX to allocate a struct hcicplebigcreate_sync on the stack with room for 0x11 (17) BIS entries. However, conn->numbis can hold…
When was CVE-2026-31772 disclosed?
CVE-2026-31772 was first published in the National Vulnerability Database on May 1, 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-31772 actively exploited?
CVE-2026-31772 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31772?
CVE-2026-31772 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31772?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31772, 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-31772

Explore →

Is Your Infrastructure Affected by CVE-2026-31772?

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