CVE-2026-31772Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 91d19383b7ed035e22165ae5c836e50bb9f95fbe before f5d446624345d309e7a4a1b27ea9f028d6a8c5d9; from 42ecf1947135110ea08abeaca39741636f9a2285 before aba0aea354015794e8312dd7efe726967e58aefe; from 42ecf1947135110ea08abeaca39741636f9a2285 before eaf32002ca7b1ba51c9f140991fd9febe6de79f0; from 42ecf1947135110ea08abeaca39741636f9a2285 before bc39a094730ce062fa034a529c93147c096cb488; 8958e1cee4e2eac1a5b825caa4dd96ce9ed975dd; from 6.12.2 before 6.12.81; from 6.11.11 before 6.12 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.11.11 before 6.12; from 6.12.2 before 6.12.81; from 6.13.1 before 6.18.22; from 6.19 before 6.19.12; 6.13; 7.0; 7.0; 7.0; and 3 more ranges | NVD |
References
- https://git.kernel.org/stable/c/f5d446624345d309e7a4a1b27ea9f028d6a8c5d9patch
- https://git.kernel.org/stable/c/aba0aea354015794e8312dd7efe726967e58aefepatch
- https://git.kernel.org/stable/c/eaf32002ca7b1ba51c9f140991fd9febe6de79f0patch
- https://git.kernel.org/stable/c/bc39a094730ce062fa034a529c93147c096cb488patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.