CVE-2026-31772

Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync

HIGH
7.8
CVSS Score
Published: May 1, 2026 at 02:15 PM UTC
Updated: October 19, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.11.11 ≤ v < 6.126.12.2 ≤ v < 6.12.816.13.1 ≤ v < 6.18.226.19 ≤ v < 6.19.1242ecf1947135110ea08abeaca39741636f9a22856.11.116.12.26.137.07.0 rc17.0 rc27.0 rc37.0 rc47.0 rc57.0 rc68958e1cee4e2eac1a5b825caa4dd96ce9ed975dd91d19383b7ed035e22165ae5c836e50bb9f95fbe
Vendor states this is fixed in aba0aea354015794e8312dd7efe726967e58aefe (fixed)
Vendor states this is fixed in bc39a094730ce062fa034a529c93147c096cb488 (fixed)
Vendor states this is fixed in eaf32002ca7b1ba51c9f140991fd9febe6de79f0 (fixed)
Vendor states this is fixed in f5d446624345d309e7a4a1b27ea9f028d6a8c5d9 (fixed)
Affected range stops below 6.12, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.81 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.22 (unaffected)
Vendor states this is fixed in 6.19.12 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787CWE-121

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card