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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
3.9%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 11, 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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 41× 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 130 total refreshes for this CVE.

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

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 May 11, 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 3.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.