Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.81, 6.12, 6.18.22, 6.19.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 91d19383b7ed035e22165ae5c836e50bb9f95fbe · fixed in f5d446624345d309e7a4a1b27ea9f028d6a8c5d9; From 42ecf1947135110ea08abeaca39741636f9a2285 · fixed in aba0aea354015794e8312dd7efe726967e58aefe; From 42ecf1947135110ea08abeaca39741636f9a2285 · fixed in eaf32002ca7b1ba51c9f140991fd9febe6de79f0; From 42ecf1947135110ea08abeaca39741636f9a2285 · fixed in bc39a094730ce062fa034a529c93147c096cb488; From 6.12.2 · fixed in 6.12.81; From 6.11.11 · fixed in 6.12
- Linux Linux
6.13
- KernelLinux
fixed in 6.12.81; From 6.13.0 · fixed in 6.18.22; fixed in 6.19.12